RFC: svn for make fetch
in [Ports]
|
Prev: Improving Ada support on FreeBSD and in the ports system
Next: New port: sysutils/megacli waiting to commit
From: Xin LI on 9 Nov 2009 17:28 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eitan Adler wrote: > I was hoping to get a bit more of a response to a recent posting of > mine with regard to using svn to fetch files for ports > My proposal: http://www.mail-archive.com/freebsd-ports(a)freebsd.org/msg23776.html > A summary of what has been going on: > http://wiki.freebsd.org/EitanAdler/ports-svn > > This is something that more than 2 people should have an input on Just my $0.02 but I think it would be great if we can do: - "make fetch" would prefer using a pre-packaged tarball, but fallback to a svn/whatever checkout with a specific revision number, then generate a tarball from the export. - "make checksum" would check the tarball's checksum. Maybe we can also have some variables to control that we actually want the 'HEAD' revision without checking any checksum. However, I think it would be nice if we can do a checksum'ed checkout for specific SCM revision, especially if we want to have ports to work not only for *-devel ports where we would prefer signed source code. Cheers, - -- Xin LI <delphij(a)delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkr4l6QACgkQi+vbBBjt66CD/wCbBcIFcfbK4a0533PAcNxbZuV5 WXAAnjQfl07w/vcHicVS0s+FOrOs5CMS =1Hly -----END PGP SIGNATURE----- _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Brooks Davis on 9 Nov 2009 17:52 On Mon, Nov 09, 2009 at 02:28:52PM -0800, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Eitan Adler wrote: > > I was hoping to get a bit more of a response to a recent posting of > > mine with regard to using svn to fetch files for ports > > My proposal: http://www.mail-archive.com/freebsd-ports(a)freebsd.org/msg23776.html > > A summary of what has been going on: > > http://wiki.freebsd.org/EitanAdler/ports-svn > > > > This is something that more than 2 people should have an input on > > Just my $0.02 but I think it would be great if we can do: > > - "make fetch" would prefer using a pre-packaged tarball, but fallback > to a svn/whatever checkout with a specific revision number, then > generate a tarball from the export. > - "make checksum" would check the tarball's checksum. It's probalby not practical to generate an archive with consistently identical checksums due to the various timestamps (at least without adding a tar writer to svn which would be kind of cool. :) > Maybe we can also have some variables to control that we actually want > the 'HEAD' revision without checking any checksum. However, I think it > would be nice if we can do a checksum'ed checkout for specific SCM > revision, especially if we want to have ports to work not only for > *-devel ports where we would prefer signed source code. While this wasn't the intent of the -DBOOTSTRAP stuff I added to the llvm port, people are finding it useful so if we can find I clean way to support this I think it would be cool. -- Brooks
From: Eitan Adler on 10 Nov 2009 01:51 Correct me if I'm wrong but I thought that svn did its own checksumming. If so why do we need to our own? _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Peter Pentchev on 10 Nov 2009 05:32 On Tue, Nov 10, 2009 at 08:51:25AM +0200, Eitan Adler wrote: > Correct me if I'm wrong but I thought that svn did its own checksumming. > If so why do we need to our own? Subversion's checksumming makes sure that you get exactly the same files that are on the Subversion server at this particular moment in time. The Ports Collection's distfile checksums make sure that you get exactly the same files *as the port maintainer examined at some previous moment in time*. The difference is crucial. svnadmin create /home/svn/foo svn import http://.../foo/trunk/mycoolproject <create a port of mycoolproject> rm -rf /home/svn/foo svnadmin create /home/svn/foo svn import http://.../foo/trunk/mycoolproject ...and suddenly the port fetches something completely different. G'luck, Peter -- Peter Pentchev roam(a)ringlet.net roam(a)space.bg roam(a)FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This would easier understand fewer had omitted.
From: Jonathan on 10 Nov 2009 09:04
On 11/8/2009 10:31 AM, Eitan Adler wrote: > I was hoping to get a bit more of a response to a recent posting of > mine with regard to using svn to fetch files for ports > My proposal: http://www.mail-archive.com/freebsd-ports(a)freebsd.org/msg23776.html > A summary of what has been going on: > http://wiki.freebsd.org/EitanAdler/ports-svn > > This is something that more than 2 people should have an input on I would learn toward having something available to create tarballs for maintainers but I don't think having a port fetch directly from svn would be such a good idea. Also what about the load on the repository? There is a lot of infrastructure in place for mirroring tarballs (FreeBSD and otherwise) but very little for svn and I doubt many projects have mirrored repositories. Going with the mplayer example there may not be a lot of FreeBSD users installing mplayer at any given time but it may be enough to be a concern as far as load on the repository. Jonathan _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |