You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation says that it is "luck" that basefs is processed first, but unluckily the -p package gets processed first if it is in the same folder (inode order?). This breaks if my -p package uses /dev or /bin folders - it will have to create these folders and then basefs will fail. A workaround is to make build-filesystem-ng allow multiple (or rather duplicate) defines of folders (patch available).
This issue is part of what is explained under "Futures" in Documentation/build-filesystem-ng.md but it might be worth tracking it here.
The text was updated successfully, but these errors were encountered:
The documentation says that it is "luck" that basefs is processed first, but unluckily the -p package gets processed first if it is in the same folder (inode order?). This breaks if my -p package uses /dev or /bin folders - it will have to create these folders and then basefs will fail. A workaround is to make build-filesystem-ng allow multiple (or rather duplicate) defines of folders (patch available).
This issue is part of what is explained under "Futures" in Documentation/build-filesystem-ng.md but it might be worth tracking it here.
The text was updated successfully, but these errors were encountered: