| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ciaran McCreesh schrieb: |
| 5 |
>> Your description is fancy ... _but_ the things you are describing is |
| 6 |
>> an integrated GUI. It's on the same level the CLI is on. |
| 7 |
>> This is nothing which is achievable with catapult (at least at the |
| 8 |
>> moment). Catapult _uses_ the package manager and is not part of it. |
| 9 |
>> Thus also the GUI would _use_ the PM. |
| 10 |
> |
| 11 |
> And thus the GUI will end up delivering a half-arsed minimally |
| 12 |
> functional toy. That isn't what users need. |
| 13 |
|
| 14 |
This ended in a fully functional tool - but with a restricted feature |
| 15 |
set. This isn't an issue for most users though - because the additional |
| 16 |
features won't be needed by most users. |
| 17 |
|
| 18 |
Again: There is a working GUI with it's user base already existing, |
| 19 |
which _can_ use Catapult already. And I won't describe it as "minimally |
| 20 |
functional toy". |
| 21 |
|
| 22 |
>> And as mentioned in my earlier mail, avoiding the exec() stuff and use |
| 23 |
>> the manager itself is bad in my eyes for different reasons. And for |
| 24 |
>> portage it won't work at all. |
| 25 |
> |
| 26 |
> You could implement it for Portage by using exec() yourself... |
| 27 |
> |
| 28 |
|
| 29 |
To be honest, this is something I haven't thought about yet ... |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 32 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 33 |
|
| 34 |
iD8DBQFH83wI4UOg/zhYFuARAq8pAJ4mDNWqHwaTTL8tptuB/99MVkvnrgCeNBVB |
| 35 |
LAMM2k9aJAb3WCYWJg6lqE4= |
| 36 |
=pLOp |
| 37 |
-----END PGP SIGNATURE----- |
| 38 |
-- |
| 39 |
gentoo-guis@l.g.o mailing list |
Archives