From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] future restrictions to DISTDIR access from the ebuild env
Date: Wed, 24 Aug 2005 17:43:51 -0500 [thread overview]
Message-ID: <20050824224351.GB1701@nightcrawler> (raw)
[-- 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 --]
reply other threads:[~2005-08-24 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050824224351.GB1701@nightcrawler \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox