xdg question w.r.t cmake

[Thiago Macieira]

Alexander Neundorf wrote:
>> Reading of those is controlled by $XDG_CONFIG_DIRS and $XDG_DATA_DIRS
>> (the latter, int his case). Which means that whatever we install to,
>> it must be loaded in those variables.
>
>$XDG_CONFIG_DIRS and $XDG_DATA_DIRS are environment variables here,
> right ? What do you mean with "Reading of those" ?

I meant programs looking for resources that are in the XDG directories. 
That is not the case here, since we're not looking for the resource, 
we're installing it.

>> To be noted:
>> - like I said, $XDG_*_DIRS must include the location where KDE
>> installed to. So if the user installed somewhere else than /usr or
>> /usr/local, the variables MUST be modified.
>
>The environment variables you mean ?

Yes.

>> I just don't know if we should do it in
>> startkde or if we should force the user to do it.
>
>Any opinion whether it would make sense to put the macros for the
> mimetypes, the icon cache and maybe also xdg-utils (not used by KDE
> AFAIK ?) into a FindXdg.cmake or would this be wrong ?

For KDE, the script is already correct. We should NOT use the environment 
variables. We should completely ignore them.

For a third-party application, I also recommend to stick to one's prefix. 
If the user chooses a prefix that is not /usr or /usr/local, he's got a 
reason for that and he'll have to adjust the environment variables.

For a binary application installing and using XDG, I'd say ignore 
completely the variables and install directly to /usr or /usr/local.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070724/44197867/attachment.sig>