| 1 |
On Sat, 06 Sep 2014 09:03:13 -0400 |
| 2 |
"Anthony G. Basile" <blueness@g.o> wrote: |
| 3 |
> Note that, as with the Metadata Cache, these variable should be stored |
| 4 |
> with all the conditionals evaluated. |
| 5 |
|
| 6 |
Paludis doesn't do this (and historically, Portage didn't either). We |
| 7 |
store USE etc. This is useful because it allows us to detect when |
| 8 |
people have been mucking around with DEPEND and the like. |
| 9 |
|
| 10 |
> A list of all files belonging to the package, along with a designation |
| 11 |
> of the file type (regular, directory, symlink, pipe, etc), MD5SUM or |
| 12 |
> other checksum, and mtime time. |
| 13 |
|
| 14 |
Packages aren't allowed to install pipes. |
| 15 |
|
| 16 |
> A list of all executable or shared objects for each package and the |
| 17 |
> corresponding linking information, including full path to the object, |
| 18 |
> its architecture and ABI, SONAME, RPATH and any NEEDED objects they |
| 19 |
> link against, as reported by `readelf` on ELF systems, or similar |
| 20 |
> tools for other executable formats. Currently this information is |
| 21 |
> being cached by Portage in NEEDED.ELF.2, NEEDED.MACHO.3, NEEDED.XCOFF, |
| 22 |
> NEEDED.PECOFF, etc. |
| 23 |
|
| 24 |
This is utterly arbitrary, and introduces a dependency on particular |
| 25 |
non-standard package whose behaviour we don't control. Not everything |
| 26 |
is C and ELF, and we shouldn't be encouraging "solutions" that make |
| 27 |
the assumption that they are... |
| 28 |
|
| 29 |
You've also not discussed how this interacts with Portage's |
| 30 |
package.provided misfeature. |
| 31 |
|
| 32 |
Finally, you don't have any way of using this information, since you |
| 33 |
don't have a way of knowing what packages are installed. |
| 34 |
|
| 35 |
-- |
| 36 |
Ciaran McCreesh |
Archives