Created attachment 145060 [details]
This is a binary package for cvsup-without for FreeBSD/amd64, compiled statically for 7.4-RELEASE.
I think I must deny this request.
The ports tree is only required to support the following releases:
8.4, 9.1, 9.2, 9.3, and 10.0
Any support for earlier release is actively removed, so there's no way a new port only for FreeBSD 7.4 will be approved for integration. Sorry!
(In reply to John Marino from comment #1)
> I think I must deny this request.
> The ports tree is only required to support the following releases:
> 8.4, 9.1, 9.2, 9.3, and 10.0
> Any support for earlier release is actively removed, so there's no way a new
> port only for FreeBSD 7.4 will be approved for integration. Sorry!
Sorry if I haven't made it clear -- the port is compiled on 7.4-RELEASE but it's intended for supported releases because a bug with ezm3 would cause coredumps on supported releases..
Can you explain what the use case of cvsup* is? I am under the impression there are no active cvs repositories.
In other words, who would use such a port and how/why?
(In reply to John Marino from comment #3)
> Can you explain what the use case of cvsup* is? I am under the impression
> there are no active cvs repositories.
> In other words, who would use such a port and how/why?
Anybody who needs a local NetBSD CVS repository mirror (and probably also other CVS repositories that is distributed via CVSup) or using CVSup for their own projects.
There is supposedly a better (and conflicting) version of cvsup provided with the lang/modula3 port.
You stated the purpose of this new port is due to an ezm3 bug. Is this new port still needed if the modula3 cvsup works fine?
hmm, I just remembered modula3 doesn't build on many platforms (e.g. FreeBSD 9+ on amd64 only)
but this port is also limited to amd64 so it's about a wash...
(In reply to John Marino from comment #5)
> another question:
> There is supposedly a better (and conflicting) version of cvsup provided
> with the lang/modula3 port.
> You stated the purpose of this new port is due to an ezm3 bug. Is this new
> port still needed if the modula3 cvsup works fine?
No, we don't need a binary-only port assuming the source port is buildable and in a working condition.
i would love it if you could test the modula3 version of cvsup and see if it works well. Nobody has really done that (and it is kind of hidden where it is)
(In reply to John Marino from comment #8)
> i would love it if you could test the modula3 version of cvsup and see if it
> works well. Nobody has really done that (and it is kind of hidden where it
Just an update -- I didn't forget this, but cvsup was quite slow so I was only able to finish one run so far :)
There are some difference between modula3 version and the ezm3 version. For instance, if umask=002 is specified in supfile, modula3 version will not apply the right permissions while ezm3 version does. Any idea?
No, sorry, I'm not familiar with cvsup really.
It's possible that ezm3 version has local patches to alter the standard behavior of cvsup. I vaguely remember seeing something like that. I guess you could check the port source and see if that's where the difference originates.
anything new here?
I'd love an update on this. The PR is under my name but if nothing changes I'll just release it "back to the heap".
Sorry I don't have much energy to figure out what customization in ezm3 is at this moment, which is why I end up creating a binary port :(
In summary, the status quo is:
- lang/modula3 ships with a mostly usable version of cvsup that have problems in the corner cases like handling file permissions, uses more memory and is slower, which we need to either figure out why or have someone to find out why and fix.
- lang/ezm3 and net/cvsup is scheduled for removal soon.
- The binary port is created to fill the gap just in case, for now, both client and server side worked fine.
Okay, you are correct that ezm3 and cvsup* ports are getting removed and that seems that it will happen. That might be justification enough for this port although it only works for amd64. It's better than nothing, I guess.
I think I'll just call the port "cvsup-static" since it will be the only cvsup port
A commit references this bug:
Date: Tue Sep 9 10:39:07 UTC 2014
New revision: 367724
Add new port net/cvsup-static
The ports lang/ezm3, net/cvsup and net/cvsup-without-gui ports have
expired and will be removed as soon as today. This port provides
a statically-compiled version of cvsup-without-gui to offer cvsup on
the amd64 platform of all supported releases of FreeBSD.
This hasn't been available since ezm3 coredumps on newer releases, and
now it's BROKEN due to being unstaged.
Submitted by: delphij@
Later I will add a conflict between this and modula-3 (I'll modify modula-3 after cvsup* ports are removed to remove conflict with those and add a conflict with this port)