* [gentoo-portage-dev] future restrictions to DISTDIR access from the ebuild env
@ 2005-08-24 22:43 Brian Harring
0 siblings, 0 replies; only message in thread
From: Brian Harring @ 2005-08-24 22:43 UTC (permalink / raw
To: gentoo-portage-dev; +Cc: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Hola all.
robbat2 made the suggestion, and after a bit of playing I think it's
best- in short, to support multiple DISTDIR's, we need either
intelligent querying of portage from bash side as to a files true
location, or a directory full of symlinks pointing at the ebuild's
stated files.
Latter is easiest imo, and a bit cleaner for a dev to be able to look
at it and see why things are breaking; upshot, adding this indirection
allows portage (with sane fetcher(s)) to do N DISTDIR, and it also
causes any ebuild that has unstated SRC_URI deps to bail.
The forced bail pretty much makes it so that an ebuild dev can't
easily screw up, they hit the unpack failure rather then a commit and
a user hitting it.
If you've got issues with it, give a yell; just added this in the
rewrite.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-08-24 22:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-24 22:43 [gentoo-portage-dev] future restrictions to DISTDIR access from the ebuild env Brian Harring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox