[pacman-dev] [abs] Proto files and Makeworld

[eliott]

On 1/6/08, Dan McGee <dpmcgee at gmail.com> wrote:
> On Jan 6, 2008 1:31 PM, eliott <eliott at cactuswax.net> wrote:
> >
> > On 1/6/08, Travis Willard <travis at archlinux.org> wrote:
> > > On Jan 6, 2008 12:08 PM, Dan McGee <dpmcgee at gmail.com> wrote:
> > > > On Jan 4, 2008 9:11 AM, Travis Willard <travis at archlinux.org> wrote:
> > > > > Hey guys,
> > > > >
> > > > > With ABS splitting off from pacman, I was wondering where makeworld and the
> > > > > .proto files belonged.
> > > > >
> > > > > To me, makeworld seems to be an abs tool (and even mentions ABS in its
> > > > > usage) so it would seem to belong in the abs project, not with pacman
> > > > > itself.
> > > >
> > > > Done...hope I didn't steal your thunder here. See the current abs.git
> > > > repo (I promise I'll try not to touch it anymore! haha).
> > >
> > > Onoz!  I am less a man - Dan hath touched mine sacred ABS project.
> > >
> > > Heh - thanks for moving that over.
> > >
> > > > > The proto files (PKGBUILD.proto, install.proto, and possibly a
> > > > > ChangeLog.proto?) seem to belong with makepkg in my mind.  Any changes in
> > > > > these proto files would be directly caused by changes to makepkg, and the
> > > > > coupling of putting them in with the pacman package seems to make sense.
> > > > > I've never understood why we sync them with abs in the first place - if
> > > > > someone wants a prototype PKGBUILD to start from, why should they have to
> > > > > download the entirety of our repos' build scripts?
> > > >
> > > > And also done. They now live in the top level of the pacman
> > > > repository, and they are installed (at least on Arch) to
> > > > /usr/share/pacman/.
> > >
> > > I'll do the same with the "non-standard" prototypes and throw them in
> > > the same location in the abs package... when I make the ABS package,
> > > that is.
> > >
> > > OH - I'm going to need core access, and I'll either need to bug eliott
> > > to add an rsync stanza for ABS, or get the permissions to add it
> > > myself, so I can test out this new rsync-style ABS and get it working
> > > up to snuff.
> >
> > Just let me know what you want added, and I will add it.
> > This is what I had for testing at one point.
> >
> > [abstest]
> >     hosts allow = <myip>
> >     path = <dir in my home dir>
> >     comment = abs test 4 eliott
> >     list = false
> >     exclude = CVS
> >     read only = true
> >     #refuse options = c compress
> >     #dont compress = *
> >
> > I was fiddling with the compression options.
> > Compression adds alot of cpu overhead, and turning it off (forcing it
> > off) yeilded much better server side load reduction. However, it used
> > a bit more bandwidth... *shrug*
> >
> > > How were we generating the tree for that again?  Commit/tag hooks?
> > > Something in the db-repo scripts?  And, for that matter, where would
> > > be a good place to locate the generated ABS tree server-side?
> > > /var/abs?
> >
> > In my testing I was using a cronjob that updated the tree periodically.
> > Not sure how it should be done in the long run...
> >
> > As to dir location on gerolde, not sure.
> > I think abs lives in /home/abs/ right now.
>
> /srv/abs_rsync ?

Keep in mind that with the way gerolde is setup, /home has lots of
space, while some of the other mount points do not. :/

Do a df -h to see what i mean.