Summary: | New QA check: warn about invalid/deprecated paths | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Conceptual/Abstract Ideas | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | qa |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925, 361759 |
Description
Diego Elio Pettenò (RETIRED)
2009-06-09 02:01:27 UTC
Hi Diego, I don't get exactly what you are asking for here. I assume the end result is that: Files should not be installed into these paths. We can possibly utilize sandbox here. We can't disallow use of all these paths because existing ebuilds may need to clean up old data in old locations. Is this the extent of your request? -A *** Bug 280853 has been marked as a duplicate of this bug. *** I wanted same for X11 app-defaults directory in bug 280853 which should always be in /usr/share/X11/app-defaults or otherwise it simply won't work. It used to be in /etc and before that, in /usr/X11R6 and we still have unupdated ebuilds in tree. Can we _please_ revisit this? Seems like new packages get actually added using these paths still, and at least those should be stopped. Please at least add a warning in the build, and die only on stricter, for now if you prefer. This is in git now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=4faf6bc8c15124ea2f8bfb7b7c6212762b511b77 This is fixed in 2.1.9.3 and 2.2_rc79. |