| 1 |
Peter Volkov wrote: |
| 2 |
> This means that every ebuild which uses 'unpack ${A}' should have in |
| 3 |
> DEPEND a program which is selected by filename extension of sources. So |
| 4 |
> as I understood your initial suggestion was to make this happen |
| 5 |
> automatically. And this is very logical as makes ebuilds cleaner and |
| 6 |
> more terse. So why did you changed your mind and try to write another |
| 7 |
> eclass (which then should sit in the tree forever), to create duplicate |
| 8 |
> unpack function instead of just making step you suggested initially? Is |
| 9 |
> there any intension to remove unpack logic from package manager? And if |
| 10 |
> yes, why? |
| 11 |
|
| 12 |
++ |
| 13 |
|
| 14 |
I also was wondering this. And if we add "unpack2()", which could be a |
| 15 |
little hard to explain in the documentation, it will need to be there at |
| 16 |
least until ebuilds stop using it (when portage gets this functionality |
| 17 |
ultimately). |
| 18 |
|
| 19 |
For my uses, I'd rather do deps manually and use the official portage |
| 20 |
unpack() until portage has such features in order to keep my ebuilds |
| 21 |
looking a bit more clean. |
| 22 |
|
| 23 |
-Joe |
Archives