> Date: Wed, 03 Jul 2013 12:40:42 -0500
> From: Bruce Dubbs <bruce.du...@gmail.com>
> Subject: [blfs-dev] BLFS Package Currency
>
> One of the more difficult things that I've found about BLFS is to
> determine whether a package in the book is current or not. I've
> decided to work on a set of scripts to help with that.
>
.
.
>
- my understanding is that:
----
* BLFS has been mandated, by yourself and others, and for the foreseeable
future, to be rolling-'release' (and there was some discussion on the
pros'n'cons of that).
* you want to track upstream formal, numbered-version, official,
non-dev-branch, non-"rolling", tarball releases ....
* .... 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).
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.
rgds,
akh
--
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
