Summary: | Use the system PORTDIR for packages.g.o ? | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Component: | [OLD] gpackages | Assignee: | Gentoo Packages Website <gpackages> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | ||
Priority: | Lowest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeremy Olexa (darkside) (RETIRED)
2011-03-27 04:34:14 UTC
+1 on at least using the same PORTDIR for QA+gpackages. Not sure if we should having a full PORTDIR for system use however. (In reply to comment #1) > Not sure if we should having a full PORTDIR for system use however. It might be rude to ask third party script writers to support a non-standard PORTDIR. Anyway, I don't see a problem with it - what's the concern? Any tool wanting to use the contents of PORTDIR should be willing to read the variable. Everything I know is capable of doing so. Just more that we get better subjective results when all of our boxes use the same PORTDIR contents for building. |