| 1 |
On Wed, 17 May 2006 12:06:09 -0700 Brian Harring <ferringb@×××××.com> |
| 2 |
wrote: |
| 3 |
| Clarify on virtuals please. Unless you're mangling the data for |
| 4 |
| sym/dir, that's an unmerge time decision (as such it's not vdb data |
| 5 |
| specific). |
| 6 |
|
| 7 |
We're faking new-style virtuals for old-style virtuals, so things end |
| 8 |
up in vdb that don't have an associated 'real' ebuild. Portage can't |
| 9 |
unmerge them, and it has some trouble with the reduced-content entries |
| 10 |
for these too. |
| 11 |
|
| 12 |
| > We went over this already. Remember webapp.eclass? |
| 13 |
| |
| 14 |
| Nope. Assume I'm stupid, don't ask a question when I ask for an |
| 15 |
| answer, just state it please- saves both you and I time. |
| 16 |
| |
| 17 |
| Do recall they were triggering merge -C calls on their own, but |
| 18 |
| that's not portage incompatibility as much as doing something dumb... |
| 19 |
|
| 20 |
And that's exactly it. At what point does something stop being API and |
| 21 |
start being "someone is doing illegal things with internals"? |
| 22 |
|
| 23 |
| Ebuild is easy- I'm pointing at it because the local env issue should |
| 24 |
| rear it's head there. It's also a tool that ebuild devs rely on |
| 25 |
| fairly heavily for debugging, as such two birds one stone (locals |
| 26 |
| issue you get to investigate closer, and you flesh paludis out |
| 27 |
| further). |
| 28 |
|
| 29 |
Actually, I was planning to handle that one by BREAK_FUNCTIONS (name |
| 30 |
sucks and is not final), which is kinda like SKIP_FUNCTIONS but rather |
| 31 |
than skipping, launches an interactive shell. |
| 32 |
|
| 33 |
| > Portage still relies upon being able to source ebuilds, even if |
| 34 |
| > their EAPI isn't supported. |
| 35 |
| |
| 36 |
| Paludis doesn't? |
| 37 |
|
| 38 |
Nope. Paludis can sanely (as in, treat as EAPI masked) handle ebuilds |
| 39 |
that bash can't parse. This paves the way for XML-based ebuilds, which |
| 40 |
as we all know is a critical feature required for enterprise support. |
| 41 |
|
| 42 |
| Related, doc this stuff out please. Portage differences doc you've |
| 43 |
| got is more "we're better cause of xyz"- which is fine, but a low |
| 44 |
| level "this is what we do differently" (metadata/security fex) would |
| 45 |
| at least allow the possibility of folks being on the same page. |
| 46 |
|
| 47 |
Yeah, that's something that would be useful. I was trying to get spb to |
| 48 |
do it... |
| 49 |
|
| 50 |
-- |
| 51 |
Ciaran McCreesh |
| 52 |
Mail : ciaran dot mccreesh at blueyonder.co.uk |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-dev@g.o mailing list |
Archives