| 1 |
On 23 June 2011 09:46, Zac Medico <zmedico@g.o> wrote: |
| 2 |
|
| 3 |
> It could be implemented with a metadata.xml extension, or possibly an |
| 4 |
> new ebuild variable. A GLEP would be a good way to propose such an |
| 5 |
> extension. |
| 6 |
|
| 7 |
I'd myself see metadata.xml or ebuild variables, on their own, less |
| 8 |
than useful. |
| 9 |
|
| 10 |
For me, the primary benefit of the category system is it makes it easy |
| 11 |
to locate and install packages I wish to install, and hidden metadata |
| 12 |
stored in the package itself would prove very unhelpful in this |
| 13 |
regard. |
| 14 |
|
| 15 |
In order for this metadata to be of any use to a user, it would need |
| 16 |
to have some way to facilitate its use, whether it be a fake generated |
| 17 |
directory of symlinks, or a dedicated program ( like debians aptitude |
| 18 |
) for exploring this data in a tag-oriented way. |
| 19 |
|
| 20 |
( And any solution which requires software to iterate and index the |
| 21 |
entirety of portage to accumulate this tag data, user side, will be |
| 22 |
considerably unfavourable in my eyes ) |
| 23 |
|
| 24 |
-- |
| 25 |
Kent |
| 26 |
|
| 27 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
| 28 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
| 29 |
|
| 30 |
http://kent-fredric.fox.geek.nz |
Archives