| Summary: | Exclude lost+found from sync | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Robert Wruck <robert> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | agaffney |
| Priority: | High | ||
| Version: | 2.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Robert Wruck
2006-09-17 07:15:58 UTC
Uhh, why? There isn't anything on a separate /usr/portage that can't be easily replaced. You can also added it locally to PORTAGE_RSYNC_EXTRA_OPTS in make.conf I'd prefer that we didn't have to exclude /packages and /distdir, but that's just they way that is because sombody thought it would be okay to stick those *inside* PORTDIR. So, I'd rather not add anything more to the default excludes... Well, I agree that recovering files from /usr/portage would be most easily done using emerge --sync, unless you had some huge amount of pre-built packages (also agree about packages and distfiles, but that's a different story). Although I don't have any pre-built packages myself, I'd think that lost+found is some kind of "special" directory that should not be silently discarded as a side effect of --sync. That decision should be up to the admin and default policy should be to keep it IMHO. See comments #1 and #2. |
