| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Wednesday 23 June 2004 02:15, Marius Mauch wrote: |
| 5 |
> The problem is much deeper, currently the syntax for KEYWORDS is quite |
| 6 |
> strict, any enhancements require portage changes on user systems. |
| 7 |
O.k., I'm on thin ice here, because I don't know enough about portage. Why not |
| 8 |
stripping either "status" or "+" from the keyword list for all operations |
| 9 |
where it is not needed? Couldn't it be transiently stored in an extra field, |
| 10 |
until everything is in place to migrate users without any hassle? |
| 11 |
|
| 12 |
> > Just had another thought about the "re-arranging arch" option. How do |
| 13 |
> > you implement this in a differend backend, e.g. a database, Aron? |
| 14 |
> |
| 15 |
> What do you mean here, a backend for the tree, the cache or what? |
| 16 |
A possible future - no file tree, but everything stored in a db. When each |
| 17 |
keyword is a column in a table, you cannot reorder them as in an ebuild |
| 18 |
|
| 19 |
|
| 20 |
Carsten |
| 21 |
-----BEGIN PGP SIGNATURE----- |
| 22 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 23 |
|
| 24 |
iD8DBQFA2ZvcVwbzmvGLSW8RAmvCAJ0WUmHFERcg3AeUDR0tgrJy3/Il/gCgnFe5 |
| 25 |
n91cT88yAXX6dQTDkjeV/dY= |
| 26 |
=o459 |
| 27 |
-----END PGP SIGNATURE----- |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives