Changes between Initial Version and Version 1 of Ticket #1739, comment 11
- Timestamp:
- 12/29/2024 02:09:41 PM (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1739, comment 11
initial v1 7 7 So I'd propose two possible approaches here: 8 8 - if the LFS book is modified: let the user define the name and group of the temporary user (default lfs:lfs, but could also be cosette:miserables or whatever). This user and group shouldn't exist on the machine and would be removed before entering chroot (as bdubbs said, there is no need to keep it further on an automated build) 9 - if the LFS book isn't modified: roughly keep the present state of trunk, except if an lfs user already exists, it is moved to another name before creating a temporary one. The temporary one would be deleted before entering jhalfs, and the moved one would be left as is (possibly with a warning at the end of the jhalfs run).9 - if the LFS book isn't modified: roughly keep the present state of trunk, except if an lfs user already exists, it is moved to another name before creating a temporary one. The temporary one would be deleted before entering chroot, and the moved one would be left as is (possibly with a warning at the end of the jhalfs run). 10 10 11 Note that bdubbs made the a good point telling that the temporary user is only needed to stay in a manual build, to be able to fix errors in chap. 5 and 6, but not in an automatedbuild...11 Note that bdubbs made a good point telling that the temporary user is only needed to stay in a '''manual''' build, to be able to fix errors in chap. 5 and 6, but not in an '''automated''' build...