| 1 |
On Fri, 7 Jul 2017 12:48:04 -0400 |
| 2 |
NP-Hardass <NP-Hardass@g.o> wrote: |
| 3 |
|
| 4 |
> There is actually a huge functional difference between the two that you |
| 5 |
> are missing here. A meta package defines its dependencies in full |
| 6 |
> dependency syntax. This means you can specify versions, USE flag |
| 7 |
> dependencies, make packages dependent on USE flags, etc. A package set |
| 8 |
> is just a list of packages (potentially constrained by version. TTBOMK, |
| 9 |
> there is no inclusion of any USE flag functionality in sets. |
| 10 |
> Additionally, let's say you have a more complicated dependency like || ( |
| 11 |
> A B ), I don't think there is a way to describe that in a package set |
| 12 |
> at all. |
| 13 |
|
| 14 |
Actually you can specify basic USE dependencies in sets. You can also |
| 15 |
specify SLOTs. For example, this is valid. |
| 16 |
|
| 17 |
media-libs/tiff:3[abi_x86_32,jpeg,zlib,-cxx] |
| 18 |
|
| 19 |
-- |
| 20 |
James Le Cuirot (chewi) |
| 21 |
Gentoo Linux Developer |
Archives