[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KStdDirs, named levels.
From:       iglio () fub ! it (Pietro Iglio)
Date:       1999-07-23 15:01:58
[Download RAW message or body]

At 16.03 23/07/99 +0200, you wrote:
>Waldo Bastian wrote:
>> 
>> Pietro Iglio wrote:
>> > >Have you thought about how apps should add themselves to the menu during
>> > >installation? Up till now it was enough to put the .desktop file in the
>> > >right directory.
>> >
>> > Using batch features of the menu editor (that I'll add).
>> > For example, assuming that the .desktop files have been copied in the
right
>> > dir:
>> >
>> > kmenueditor --add Konsole.desktop MyUtils/Shell/
>> > kmenueditor --remove Konsole.desktop MyUtils/Shell/
>> > kmenueditor --move Konsole.desktop MyUtils/Shell/  MyUtils/
>> >
>> > If we introduce naming for levels (think about that!):
>> >
>> > kmenueditor --level=local --add Konsole.desktop MyUtils/Shell/
>> > kmenueditor --level=global --add Konsole.desktop MyUtils/Shell/
>> > kmenueditor --level=math_lab --add Konsole.desktop MyUtils/Shell/
>> > kmenueditor --level=students_lab --add Konsole.desktop MyUtils/Shell/
>> 
>> We can make it like:
>> 
>> export
KDEDIRS=/usr/local/kde:(distrib)/usr/kde/:(math_lab)/home/math/kde:(students
)/home/students/kde:$HOME/.kde
>> 
>> The first entry always defaults to (global), the last entry always
defaults to
>> (local). Names are optional.
>> 
>> (distrib) is reserved for distributions. E.g. third party packages
should install
>> in (global), if it comes along with your distribution it should install
in (distrib).
>> 
>> It's up to the distributors to come up with sensible paths for KDEDIRS.
>
>Instead of having this 'level' you would prolly also want to be able to 
>specify the "base-path" directly...
>
>Something like:
>kmenueditor --kdedir=/usr/local/kde --add Konsole.desktop MyUtils/Shell/
>
>Since a installation script will have installed Konsole.desktop somewhere
>in /usr/local/kde/share/.... its much easier for this script to specify
>to kmenueditor "/usr/local/kde" than it is to find out which "level" this
>is supposed to be.

I like this idea. It only needs some toughts from an RPM point of view.
If the RPM script executes the line in the above example, it means that
you force installation in the global menu. If you the RPM script executes:

kmenueditor --kdedir=ASK --add Konsole.desktop MyUtils/Shell/

you cannot execute it in batch mode.
If you omit the line, you must remember to "publish" the installed application
in some menu (your menu, global menu, etc.).

-- Pietro

[prev in list] [next in list] [prev in thread] [next in thread]