On Fri, Dec 28, 2018 at 10:15:45AM -0600, Bruce Dubbs via blfs-support wrote:
> On 12/27/2018 11:54 PM, Ken Moffat via blfs-support wrote:
> > >
> > > And we do that as a part of the release process for every *stable* version
> > > of BLFS, fixing issues as we go. Of course that doen't catch every
> > > possible
> > > error. If you build packages in a different order or omit/include
> > > optional
> > > dependencies, results will probably differ. It really not possible to
> > > build
> > > everything using every combination of package order.
> > >
> > In addition, we have updated packages during the "package freeze",
> > even when there is no known need to do so (such as fixing
> > vulnerabilities), which means that the versions I have tested in the
> > pre-release testing might not be the same as those anybody else
> > tests.
>
> Generally we don't do that. If a package has not yet been "tagged" then it
> is OK since it will be tested as packages that depend on it are tested.
>
In general, I build many packages but am unable to test them until
much later. For example, logrotate - I wait until my fcrontab script
eventually rotates the logs. Similarly I build many AV libs which
need prolongued and tedious testing after my normal desktop is
complete before I'm happy that they are indeed working.
Often, I find that some new versions are released after I have built
the previous version but before I have tagged it.
ĸen
--
The Laird o’Phelps spent Hogmanay declaring he was sober,
Counted his feet to prove the fact and found he had one foot over.
-- Louis MacNeice, Bagpipe Music
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
