> Date: Thu, 04 Jul 2013 11:07:03 -0500
> From: Bruce Dubbs <[email protected]>
> Subject: Re: [blfs-dev] BLFS Package Currency
>
        .
        .
>
> > *  .... and use them to create a non-formal, non- numbered-version,
> >    non-official-, eternally dev-branch, non-tarball, rolling-, 'release'
> >    downstream ongoing work-area (aka BLFS).
> > ----
> > Aren't those kindof ... 'contradictory' (to hopefully put it politely).
>
> Not really.  When, on average, there is more than one 'stable' package 
> release every day.
>
> > Are you better, for BLFS, to aim instead to 'just' track the relevant 
> > upstream
> > repo branch-HEADs via git/svn/cvs/&c; of course, that'd still need some
> > heuristics, and not every upstream has such public-facing repos, and the
> > distinction between dev- and rel- can be quite blurred anyhow, &usw. But 
> > isn't
> > that approach a better fit for what you do with BLFS? And, continue to do 
> > the
> > (upstream-)formal-versioned-release tarball-tracking for LFS, which _does_
> > (current[sic!]ly at least) have formal versioned releases.
>
> Size matters.  There are 62 packages in LFS, 633 in BLFS, not counting 
> xorg libs and apps.  It would be a full time job just tracking what's 
> going on.  That's why I want to automate it.  LFS is done and I'm about 
> 10% through BLFS.
>


You seem to have the wrong end of the stick: the automation is not being 
queried - that's pretty obviously required. What is being queried, is why are 
you trying to auto-track _tarballs_ for BLFS instead of just auto-tracking repo 
branch-HEADs via git/svn/cvs/&c (and per the caveats above), given how BLFS is 
rolling-'release': and contrast that with LFS, which is version-released in the 
usual way, and so a more logical fit for similarly- upstream-version-released 
tarballs.

IOW, for BLFS you seem to be trying to grab static-objects (upstream tarballs) 
in order to create an intentionally non-static 'product'. Why not just go the 
whole hog for BLFS, and instead of upstream tarballs, focus on their git/&c 
repos; you can automate that just as readily as grabbing tarballs.



rgds,
akh





--
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to