Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracker task for epoch-related issues that need solving in eopkg #73

Open
Tracked by #4119 ...
ermo opened this issue Jun 27, 2024 · 0 comments
Open
Tracked by #4119 ...

Tracker task for epoch-related issues that need solving in eopkg #73

ermo opened this issue Jun 27, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@ermo
Copy link
Contributor

ermo commented Jun 27, 2024

  • Eopkg needs to be tested to ensure that it can handle moving from the various baselayout states post usr-merge script to a new baselayout with corrected merged paths in it (IE, are we sure it won't do something stupid like try to delete the /bin symlink) - Essential
  • Eopkg needs to be able to transparently move between eopkg.py2 and eopkg.py3, whilst having its LazyDB caches and its FilesDB cache regenerated on demand.
  • Eopkg needs to detect the marker file in order to move to a new repo - Essential
  • Eopkg needs to be modified so it operates on /usr before any other paths and special-case handles /bin//sbin//lib//lib64/lib32 and skips files if the equivalent file exists under /usr - Optional but highly recommended
    • This would solve the entire eopkg check thing, as well as ensuring that eopkg doesn't do anything stupid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Development

No branches or pull requests

1 participant