Re: [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files

[Svyatogor <svyatogor@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is what Debian did and many people complain about this, cause they want 
to be able to use KDE native menu system. 
Answering your question  'Why should I modify every ebuild'. Not every, but 
only the ones which provide some apps with UI. Secondly you don't *have to*. 
If you want users of your app's to edit files themselves - fair enough.

On Thursday 14 August 2003 13:56, Chris Gianelloni wrote:
> You don't.  Read the part of my comment that I left in this message.
> Rather than add OUR menu system to /usr/kde/3.1/share/applnk, we should
> patch KDE/Gnome/*box/etc (actually quite simple) to use
> /usr/share/gentoo-menu or wherever we decide the Gentoo menu should go.
> This saves the problem of having to edit every ebuild right now to
> implement this, allows for a "Gentoo Menu" support which can easily be
> turned on or off via FEATURES, and gives us a single location for our
> entire menu structure, rather than duplicating our parsed menus all over
> the filesystem.  After all, if I have Gnome, KDE, WindowMaker,
> AfterStep, and Fluxbox installed, the current proposal would have to
> create 5 separate menus and maintain them to keep everything accurate.
> Under my proposal, it would only have to maintain ONE and all 5 window
> managers would use it.  At this point you can use ANY version of ANY
> spec we wish to support, and we don't have to wait on anyone else to
> support it.

- -- 
Let the Force be with us!
Sergey Kuleshov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/O3JabYNN+aDJgscRAuMpAKDDKi1s+sSiby1IOnVpk4VX6tOKsACgssPV
YgJgLHkDGxbIrgTQSijzPZ0=
=6H43
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list