| 1 |
On 10/14/2014 02:53 AM, Duncan wrote: |
| 2 |
> Zac Medico posted on Tue, 14 Oct 2014 00:40:21 -0700 as excerpted: |
| 3 |
> |
| 4 |
>> I suggest that we add support for a |
| 5 |
>> package description index file format. For example, the attached script |
| 6 |
>> will generate a suitable index formatted as series of lines like this: |
| 7 |
>> |
| 8 |
>> sys-apps/sandbox-1.6-r2,2.3-r1,2.4,2.5,2.6-r1: sandbox'd LD_PRELOAD hack |
| 9 |
> |
| 10 |
> What about homepage? An index for it too? |
| 11 |
> |
| 12 |
> (I found myself so frequently esearching for homepage that I hacked up a |
| 13 |
> script that greps package names and homepages from the esearch results.) |
| 14 |
|
| 15 |
The intent is to use the package name/version as a "foreign key" that |
| 16 |
links an entry in the description index to an entry in one of portage's |
| 17 |
other caches. For example, the other cache could be the cache located |
| 18 |
inside the $repository/metadata/md5-cache directory (which contains the |
| 19 |
HOMEPAGE metadata that you are interested in). |
| 20 |
|
| 21 |
So, the description index serves as a fast way to initially locate a |
| 22 |
package by name or description. Then the foreign key is used to |
| 23 |
efficiently pull specific metadata from the |
| 24 |
$repository/metadata/md5-cache directory. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives