On 07/13/2018 04:08 AM, thomas wrote:
Am 2018-07-09 22:08, schrieb Bruce Dubbs:
...
In addition, upstream changes are released often. The average is
about 3.5 packages every day, seven days a week.
...
To address this, I am proposing to split BLFS into two (or possibly
more) books. My tentative names are BLFS-Basic and BLFS-Advanced.
BLFS-Basic is primarily command line tools and programs plus the basic
Xorg section of BLFS. This would be updated regularly and a 'stable'
version released every six months with the LFS book.
Just a thought:
What if we would use only *stable* versions of packages in the
BLFS-*Stable* book?
All of BLFS tries to use only stable releases now. There are some
exceptions when a package uses a development library release, but it's rare.
Ok, the book would than be not so bleeding-edge (but rock-solid i
assume). This would reduce the amount of updates we would have to make
in order to keep it on the very recent status. For example, bind
(DNS-server) had two tickets to upgrade to 9.13.1 and a few days later
to 9.13.2. Two tickets which may simply drop out if stable-book stick on
stable version 9.12.2.
Why do you think bind-9.13 is a development release? If it is and I've
missed it, I need to update the currency scripts to reflect that.
The problem here is that different packages use different methods to
designate development releases. Some use even/odd minor versions. Some
use -RCx or -dev, some use minor or point version numbers >= 80 or 90.
This list is not exhaustive.
Add to that that some developers do not bother to do development
releases. Sometimes we see three 'stable' releases in a week.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
