Opened 8 years ago
Closed 7 years ago
#1703 closed enhancement (fixed)
Allow to update LFS packages in BLFS tools
Reported by: | Pierre Labastie | Owned by: | Pierre Labastie |
---|---|---|---|
Priority: | normal | Milestone: | 3.0 |
Component: | ablfs | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
Presently, only BLFS packages are presented into the menu. Normally, all LFS packages have been built, so there is no reason to show them in the menu, except when there is a new version. In the latter case, it'd be nice to be able to select them.
Change History (8)
follow-up: 4 comment:1 by , 8 years ago
comment:2 by , 7 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 7 years ago
Version of LFS (in /etc/os-release (for systemd), /etc/lfs-release, and /etc/lsb-release) needs to be updated too...
comment:4 by , 7 years ago
Replying to pierre:
This would involve:
- [...]
- excluding gcc and shadow (and maybe systemd for systemd users) since they are in the "Beyond" book.
But we need to have the version built in LFS for those packages in the tracking dir, if they haven't been updated in BLFS yet...
comment:5 by , 7 years ago
The tracking directory may be populated from /jhalfs/logs...
Package.xml should have a <list> "LFS packages", with a <sublist> "Chapter 6", a <sublist> "chapter 8" (containing only kernel), and possibly a <sublist> "chapter 9" (for {os,lfs,lsb}-release, but that would need something special for version).
comment:6 by , 7 years ago
I think I've come to something usable at revision r3997. Will leave open in case somebody wants to comment. Also, the documentation needs to be updated!
comment:8 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Nobody commented (except Roger Koehler, who praised the addition). Closing
This would involve: