On 09/25/2018 09:13 AM, Xi Ruoyao via blfs-dev wrote:
On 2018-09-25 15:44 +0200, Pierre Labastie via blfs-dev wrote:
On 9/24/18 9:36 PM, Bruce Dubbs via blfs-dev wrote:
I think that we should work on automating most of the updating work (build,
measure, edit, and test that it fits together), so that we could concentrate
on fixing (upstream, mainly) bugs and finding the "best way" to build
problematic packages.
I'm not sure about automating package updates. In many cases a package
update is only internal and updates only require changes to statistics.
However, there are enough changes that are more than that that it
resists automation. It is also difficult to predict which category any
new package release will fit into.
Agree. I'll try to do this for LFS and BLFS once I get a new workstation
capable to compile lots of packages in a night.
The problem is BLFS, not LFS. I can do a full build of LFS in about 45
minutes if I skip tests. The number of package updates is relatively
small for LFS and I can usually do updates about twice monthly in an
afternoon.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
