From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com>
To: Gentoo Portage Development <gentoo-portage-dev@lists.gentoo.org>
Subject: [gentoo-portage-dev] [RFC] Location of Portage bash API (outside of ebuilds)
Date: Sat, 1 Feb 2014 21:08:11 +0100 [thread overview]
Message-ID: <201402012108.11867.Arfrever.FTA@gmail.com> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 880 bytes --]
bin/isolated-functions.sh contains at least 1 useful function, which could be exposed for external consumers
(without __ prefix), but must have private name (with __ prefix) when bin/isolated-functions.sh is used in
ebuild environment.
Possible solutions:
1. Make /usr/lib/portage/bin/isolated-functions.sh magically define non-private variants of useful functions
when run in non-ebuild environment.
2. Provide /usr/bin/portage.bash, which would source isolated-functions.sh (and maybe other files) and define
non-private variants of useful functions. /usr/bin/portage.bash would be easier sourceable due to PATH.
3. Provide /usr/lib/portage.bash, which would source isolated-functions.sh (and maybe other files) and define
non-private variants of useful functions.
4. Another location...
(I would probably prefer solution #2.)
--
Arfrever Frehtes Taifersar Arahesis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-02-01 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 20:08 Arfrever Frehtes Taifersar Arahesis [this message]
2014-02-02 1:52 ` [gentoo-portage-dev] [RFC] Location of Portage bash API (outside of ebuilds) Alec Warner
2014-02-05 8:08 ` Mike Frysinger
2014-02-05 19:57 ` Arfrever Frehtes Taifersar Arahesis
2014-02-06 2:21 ` [gentoo-portage-dev] " Ryan Hill
2014-02-17 8:03 ` [gentoo-portage-dev] " Mike Frysinger
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=201402012108.11867.Arfrever.FTA@gmail.com \
--to=arfrever.fta@gmail.com \
--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