| 1 |
On Wed, 25 Jun 2003 12:39:28 +0200 |
| 2 |
Paul de Vrieze <pauldv@g.o> wrote: |
| 3 |
|
| 4 |
> On Wednesday 25 June 2003 00:41, Marius Mauch wrote: |
| 5 |
> > |
| 6 |
> > BTW, I also noted the slowness of the search function, especially when |
| 7 |
> > searching in descriptions, my worst measured result was 25 minutes! Most |
| 8 |
> > likely caused by a serious lack of ram, but half an hour just to find a |
| 9 |
> > package is really annoying. |
| 10 |
> > |
| 11 |
> |
| 12 |
> This will make a nice file with all descriptions for all packages, filtered |
| 13 |
> for duplicates. Just use grep on this file instead of emerge -S and you can |
| 14 |
> find the package. If you put the creation of this file in crontab, you have |
| 15 |
> yourself a fast and flexible solution, with only 4726 lines of descriptions. |
| 16 |
> |
| 17 |
> Paul |
| 18 |
|
| 19 |
Maybe instead of having a description in the ebuild itself, there could be a single file per package cointaining the description (and maybe other stuff). That'd make searches faster. There's no point in having the description in the ebuild as it is something static that won't probably change between versions. Having it in the ebuild means (not 100% sure here) parsing the entire ebuild just to read the descr, which is too much work for a single line of text. If the number of packages continues to grow that'll become a bigger and bigger pain. |
| 20 |
|
| 21 |
Having a sepparate file for descriptions might allow one day easlily adding bigger descriptions (for the user not to need visiting the package's homepage). |
| 22 |
|
| 23 |
Josep |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives