[arch-dev-public] Tool tarball location

Aaron Griffin aaronmgriffin at gmail.com
Wed Oct 3 11:45:38 EDT 2007


On 10/3/07, Jan de Groot <jan at jgc.homeip.net> wrote:
> > -----Oorspronkelijk bericht-----
> > Van: arch-dev-public-bounces at archlinux.org [mailto:arch-dev-public-
> > bounces at archlinux.org] Namens Aaron Griffin
> > Verzonden: woensdag 3 oktober 2007 0:47
> > Aan: Public mailing list for ArchLinux development
> > Onderwerp: Re: [arch-dev-public] Tool tarball location
> >
> > On 10/2/07, Dan McGee <dpmcgee at gmail.com> wrote:
> > > On 10/2/07, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> > > > On 10/2/07, Jason Chu <jason at archlinux.org> wrote:
> > > > > Since namcap is hosted on projects now, where should the tarballs
> > go?
> > > > > ftp/other or somewhere else?  I don't think anyone's thought
> > about this
> > > > > yet...
> > > >
> > > > Yeah, let's use ftp/other/<toolname>/ for all our official stuff
> > like
> > > > pacman, devtools, etc etc.
> > >
> > > +1, although I'm not sure it was a vote. :) I would just say this-
> > > let's try to keep our FTP stuff as clean as we can since Eliott put
> > so
> > > much work into getting it that way. Obviously this stuff belongs
> > > there, but keeping it in organized folders is important.
> >
> > Yeah yeah - I mean, it's voteable sure, but it's kind of a bikeshed
> > thing. I figured we'd just go with precedent - one dir per app.
>
> What about software snapshots? We currently use
> www.archlinux.org/~name/mozilla/xulrunner-source-1.8.1.6.tar.bz2 for those
> things for example. Should we also put these snapshots in the other
> directory? I've seen these things disappearing from homedirs because of
> cleanups (gstreamer0.10-ffmpeg source was gone after arjan was
> degraded/promoted to a normal user)

Yeah - we shouldn't host this stuff in user directories. It's a little
ugly, if you ask me.

I say we stick with the precedent - logrotate, mailx, pacman, etc - we
have all these tarballs up there in ftp/other/<foo>/

It makes sense to me just to follow this




More information about the arch-dev-public mailing list