| 1 |
On 03/08/2012 12:28 PM, Michał Górny wrote: |
| 2 |
> |
| 3 |
> And something will need to provide that /usr/bin/eapi4 thing. And that |
| 4 |
> introduces new problems: |
| 5 |
|
| 6 |
I'm just parroting someone else's suggestion; I don't really know enough |
| 7 |
about the details to answer these properly. Not that that will stop me. |
| 8 |
|
| 9 |
|
| 10 |
> 1) how are we going to support multiple package managers? will we need |
| 11 |
> to install eapi4 thing as a smart wrapper choosing the right PM? |
| 12 |
> |
| 13 |
> 2) what about Prefix? #!/usr/bin/env eapi4 then, or proactive updating |
| 14 |
> of shebangs in synced ebuilds? and then regenerating the whole cache |
| 15 |
> (guess how long does it take to update it), |
| 16 |
|
| 17 |
Wouldn't #!/use/bin/env eapi4 handle both (1) and (2)? You might have to |
| 18 |
eselect package-manager or something first if you want to use two PMs at |
| 19 |
once. |
| 20 |
|
| 21 |
|
| 22 |
> 3) what should happen if user executes ebuild? the ebuild should merge |
| 23 |
> itself? with dependencies or without? |
| 24 |
|
| 25 |
If a user marks the ebuild executable and does ./foo-x.y.ebuild, the |
| 26 |
eapi4 wrapper can decide what to do. Nothing at all, print larry the |
| 27 |
cow, or crash (what we do now) are all fine with me =) |
Archives