Thanks for the offer Niklas. I mainly only need -current to maintain a couple 
of ports though, so no need. Thank you anyways.

2024-01-30T23:35:00Z Niklas Hallqvist <nik...@appli.se>:

> 
> On 2024-01-31 00:20, Stuart Henderson wrote:
>> On 2024/01/30 22:58, Johannes Thyssen Tishman wrote:
>>> Subject says it all. I'm wondering if using the git conversion of the ports 
>>> tree[0] is regarded as a good alternative to CVS for working with ports. 
>>> Are the conversion updates frequent enough to not cause any issues? Do any 
>>> of you porters use it instead of CVS? Any issues?
>>> 
>>> For the record, I've been using CVS just fine without any problems. I just 
>>> feel more comfortable with git.
>>> 
>>> [0] https://github.com/openbsd/ports
>>> 
>>> -- Johannes Thyssen Tishman
>>> https://www.thyssentishman.com
>> They are fairly frequent (currently run hourly, though this may change
>> if they start taking too long to run), but don't include the most recent
>> commit (CVS commits are not atomic, and the conversion tool is looking
>> for a different commit before it will treat the previous one as done)
>> so at certain times (especially during tree locks for release) you can
>> be waiting a while for a commit to show up.
>> 
>> Also there are no tools which successfully managed to convert branches
>> and tags in the OpenBSD CVS repo (we tried everything we could find
>> at the time when it was set up, everything which handles them had
>> some problem or other, and the range of software has not really expanded
>> since) - so the git conversion is limited to dealing with -current only
>> and there's no way to work with -stable or releases.
>> 
> I have been manually tagging and branching the stable branches for a couple 
> of years, as a basis to my personal fork of src, xenocara and ports.  And 
> then I have some scripts trying to carry over the commits made to the stable 
> branches, but they are not perfect.  I guess I could push the tags and 
> branches to my github, currently they are in a private gitlab only.
> I won't commit to support these branches though, but if someone would make 
> use of them, in the state they are, I will push them.
> 
> /Niklas

Reply via email to