Live system nochange #419
Merged
Live system nochange #419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fosslinux
force-pushed
the
live-system-nochange
branch
from
2620bdf to
c533387
Compare
Googulator
approved these changes
Jan 24, 2024
fosslinux
force-pushed
the
live-system-nochange
branch
2 times, most recently
from
42302dd to
b5e7c59
Compare
Before the simplify refactor, the convention was to name the first or default build script "<package name>.sh". The refactor changed this default to "pass1.sh", with "pass2.sh" and so on used for subsequent passes. This wasn't an issue when building usig scripts generated by script-generator (which explicitly declares the build script to use), but broke running "build <package name>" without an explicit script name from the post-bootstrap bash prompt. By deriving the script name from the current revision/pass number, this commit restores that functionality. An unfortunate blemish is that we number build scripts from 1, but repo tarballs from 0 - it would be nice to standardize on a single indexing convention.
`mke2fs` has a `-d` option that allows to populate the newly created filesystem without needing to temporarily mount it. That allows to use `parted` and `mkfs.ext3` on regular files without needing root access.
…passed (with kernel bootstrap) All distfiles are still copied to "external"
The version of stat available at that point does not support %Lr, so use instead its hexadecimal counterpar (%T)
Never actually used in the manifest, and shouldn't have been there
Allows for removal of old files or packages
Rather, uninstall existing bash before bash is built
(lol, no idea how this ever worked)
Otherwise, in --repo mode, sources are not cleaned identically to how they are in non --repo mode
fosslinux
force-pushed
the
live-system-nochange
branch
from
b5e7c59 to
438e018
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
a bunch of cleanups that make
diff -ru <(cd target; ls -R) <(cd target.bak; ls -R)be nil, wheretargetandtarget.bakhave one run normally, and the other run with--repofrom that run.There are likely a couple of checksum changes I havent added yet, and there's still a bit of work to do for
ls -lRto be nil (permissions, etc)Closes #377