On Wed, Sep 05, 2001 at 06:34:20PM -0700, Greg Stein wrote:
> On Wed, Sep 05, 2001 at 09:12:39PM -0400, Garrett Rooney wrote:
> > On Wed, Sep 05, 2001 at 06:11:06PM -0700, Greg Stein wrote:
> > > We probably should post a new tarball soon. And that kind of implies
> > > switching the tarball names to revision numbers. For example:
> > > subversion-54.tar.gz. (where 54 is the current revision of the repos)
> > it would be nice to have one with the current fixes... i'm planning
> > on putting to together a FreeBSD port skeleton for subversion soon, and
> > if i had a tarball that was more recent (say with the bsd make fix in
> > it for example) it would reduce the things i would have to change later
> > on.
> You should be able to make a tarball from the Subversion-based repository.
> In fact, we probably need to update "dist.sh" to do this.
> IOW, I'm not sure why you would need a tarball to start the ports item.
> Particularly since you just said you were able to do a checkout :-)
the problem isn't me being able to get a tarball, the problem is that
the ports infrastrucure expects to be able to go out and download one
from somewhere. at the moment, the only tarball you guys have
available is the M13 one, so it would use that.
so it isn't an issue for me starting work on a port, but if i want to
submit something, i need to base it on a specific release you guys
make, which is associated with a specific tarball, which can reliably
be downloaded from somewhere, otherwise it's not all that usefull.
as it is, i'll probably be able to throw most of this together in the
next day or two, but since i can't actually commit this to FreeBSD
myself, i have to submit a PR and let it sit in the queue for someone
else to commit. that could take a while, and if the odds are good
that you guys will put out another release soon, i might as well wait
for that, so the port has the newer functionality in it.
> Dunno whether you want the ports to run autogen.sh, or whether the port
> would contain the code from *after* that. Whatever :-)x
generally, ports go from ./configure on, so somethign along the lines
of the M3 tarball is what i'd like to have to work with.
basically all this will do is ensure the dependencies get installed
and then apply a few local patches to work with the rest of the BSD
ports (like using gdiff and gpatch so you get the gnu versions instead
of the BSD versions). it's just an automated way of compiling and
installing that allows the user to fairly easily upgrade or unistall
garrett rooney Unix was not designed to stop you from
firstname.lastname@example.org doing stupid things, because that would
http://electricjellyfish.net/ stop you from doing clever things.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Oct 21 14:36:40 2006