| 1 |
On Sat, Feb 1, 2014 at 12:08 PM, Arfrever Frehtes Taifersar Arahesis < |
| 2 |
arfrever.fta@×××××.com> wrote: |
| 3 |
|
| 4 |
> bin/isolated-functions.sh contains at least 1 useful function, which could |
| 5 |
> be exposed for external consumers |
| 6 |
> (without __ prefix), but must have private name (with __ prefix) when |
| 7 |
> bin/isolated-functions.sh is used in |
| 8 |
> ebuild environment. |
| 9 |
> |
| 10 |
> Possible solutions: |
| 11 |
> 1. Make /usr/lib/portage/bin/isolated-functions.sh magically define |
| 12 |
> non-private variants of useful functions |
| 13 |
> when run in non-ebuild environment. |
| 14 |
> 2. Provide /usr/bin/portage.bash, which would source isolated-functions.sh |
| 15 |
> (and maybe other files) and define |
| 16 |
> non-private variants of useful functions. /usr/bin/portage.bash would |
| 17 |
> be easier sourceable due to PATH. |
| 18 |
> 3. Provide /usr/lib/portage.bash, which would source isolated-functions.sh |
| 19 |
> (and maybe other files) and define |
| 20 |
> non-private variants of useful functions. |
| 21 |
> 4. Another location... |
| 22 |
> |
| 23 |
> (I would probably prefer solution #2.) |
| 24 |
> |
| 25 |
> I think 1 isn't very unix-y, 2-3 are fine. If we expect users to run it, |
| 26 |
it goes in bin, if not, then lib. |
| 27 |
|
| 28 |
-A |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
> -- |
| 33 |
> Arfrever Frehtes Taifersar Arahesis |
| 34 |
> |
Archives