| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Tue, 15 Jul 2008 04:14:18 +0200 |
| 3 |
> Marius Mauch <genone@g.o> wrote: |
| 4 |
> |
| 5 |
>> As a result of Cardoes earlier mail we talked a bit about possible |
| 6 |
>> solutions in #gento-portage, and I suggested to let portage |
| 7 |
>> automatically inject the deps based on SRC_URI pattern matching. |
| 8 |
>> A mapping of extensions and their unpack deps would be kept in the |
| 9 |
>> tree (e.g. mapping '.tar.bz2' to '( app-arch/tar app-arch/bzip2 )' |
| 10 |
>> |
| 11 |
> |
| 12 |
> Could do it just as an eclass... |
| 13 |
> |
| 14 |
> inherit work-out-my-unpack-deps-for-me |
| 15 |
> |
| 16 |
> In principle, there's nothing that can't be done on the ebuild side |
| 17 |
> here. |
| 18 |
> |
| 19 |
> For the future EAPI side, you could require package managers to define |
| 20 |
> super-magic/package-manager-unpack-bzip2 etc for whatever they use to do |
| 21 |
> the unpacking, and to make it work with existing EAPIs, use || deps |
| 22 |
> with what existing package managers happen to use as the second item. |
| 23 |
> For current EAPIs it's no worse than the existing situation, where |
| 24 |
> ebuilds have to guess that package managers use 'app-arch/unzip' to |
| 25 |
> unpack zip files. |
| 26 |
> |
| 27 |
> |
| 28 |
This is pretty close to what I had brought up in #gentoo-portage |
| 29 |
yesterday as well and seems like the best step forward. |
| 30 |
-- |
| 31 |
gentoo-dev@l.g.o mailing list |
Archives