| 1 |
You guys all have some great ideas, but I don't think I'd have enough time |
| 2 |
to be able to implement them before my project is due... especially because |
| 3 |
they appear to be a bit beyond my current programming skills. I would love |
| 4 |
to devote a lot more time to this project, but I just can't right now |
| 5 |
because I already have a lot of other things on my plate. i am really |
| 6 |
interested in contributing to Gentoo and portage in the future, though. I'm |
| 7 |
thinking this summer I'll have a chance... Anyway, I'm going to try to keep |
| 8 |
it simple and just implement a suffix trie, and hope that that provides some |
| 9 |
measurable speed improvement :] Thanks again for everyone's help, though, |
| 10 |
and I'll definitely share the (amature and minimal, sorry!) results of my |
| 11 |
project if you're interested. |
| 12 |
|
| 13 |
Emma |
| 14 |
|
| 15 |
On Mon, Nov 24, 2008 at 12:15 PM, tvali <qtvali@×××××.com> wrote: |
| 16 |
|
| 17 |
> I take it shortly together as Rene didn't catch all and so I was fuzzy: |
| 18 |
> |
| 19 |
> Portage tree has automatically updateable parts, which should not changed |
| 20 |
> by user, and overlay, which will be. Thus, index of this automatic part |
| 21 |
> should be updated only after "emerge --sync". |
| 22 |
> |
| 23 |
> Speedup should contain custom filesystem, which would be called PortageFS, |
| 24 |
> for example. In initial version, PortageFS uses current portage tree and |
| 25 |
> generates additional indexes. |
| 26 |
> |
| 27 |
> So, when you bootup, you have portage tree in /usr/portage. At some point, |
| 28 |
> PortageFS is mounted into the same directory, /usr/portage. It will map real |
| 29 |
> /usr/portage directory into /usr/portage mount point and create some |
| 30 |
> additional folders like /usr/portage/search, which maps files to do real |
| 31 |
> searches. /usr/portage/handler would be a file, where you can write query |
| 32 |
> and read result. It also contains virtual files to check dependancies and |
| 33 |
> such stuff - many things you could use with your scripts. |
| 34 |
> |
| 35 |
> When it's mounted, every change is noticed and indexes will be |
| 36 |
> automagically updated (and sometimes after communication with portage - for |
| 37 |
> example, updates when doing "emerge --sync" should not happen automagically |
| 38 |
> maybe, as it makes things slower. When it's not mounted, you can change user |
| 39 |
> files, but must run some notification script afterwards maybe to rebuild |
| 40 |
> indexes. |
| 41 |
> |
| 42 |
> Indexes are built-in into FS. |
| 43 |
> |
| 44 |
> If PortageFS is not mounted, for example because of some emergency reboot, |
| 45 |
> portage can work without indexes, using real directory instead of this mount |
| 46 |
> point. |
| 47 |
> |
Archives