KDE 3.4 conflics with Gnome 2.10

[cobaco (aka Bart Cornelis)]

--nextPart2815887.kngix2qxL9
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 11 May 2005 19:53, Adeodato Sim=F3 wrote:
> * cobaco (aka Bart Cornelis) [Wed, 11 May 2005 19:33:07 +0200]:

<off-topic context=3D"there was a CDD devcamp[1] in Valencia last week, whe=
re=20
I met, adeo, and lots of other Debianers">

 >   Hey cobaco! :)
hola (see I learned some Spanish :)=20

/me really missing the good wether from Valencia as it's raining here ;-(

</off-topic>

> > -> having this shared file owned by _any_one_ of the desktops is bound
> > to lead to endless bickering and flamewars (not to mention that it will
> > effectively force everyone to install the core of that desktop),
>
>   Yup, Christopher has already moved the file in svn,=20

good to hear :)

> and I'm really hoping that the GNOME packagers will move theirs too.=20
has anyone talked to them about it yet?

> > the right place to put this is probably the menu-xdg package, as that's
> > the package that's supposed to deal with the freedesktop menu standard
> > in Debian AIUI

hm, just realized that this is a specific case of a more general problem=20
we'll have more and more in  the future:=20
1) freedesktop standarizes certain stuff
2) different desktops come with different defaults settings for the=20
standarized stuff
3) defaults from different desktops now conflict when installed on the same=
=20
machine

luckily freedesktop base spec allows for different configuration sets=20
besides (or on top of) each other (see below)

>   This probably needs being pushed upstream, right?

I see 2 (theoretically) possible ways of pushing this upstream:
1) take defaults away from the domain of desktops into the hands of some=20
neutral 3th party (I really don't think that is gonna fly)
2) have upstream provide an xdg base-dir with their view on good default=20
settings (as far as standarized stuff goes) in some place different=20
then /etc/xdg and leave it up to the distribution/the admin(or distributor)=
=20
to activate any and/or all available config sets=20


=2D>=20
Debian doesn't need to wait for upstream to do 2 above (just move anything=
=20
upstream $DE places under /etc/xdg into /usr/share/$DE/xdg-default-config=20
or somesuch during packaging)

needs to wait for desktop-profiles to go into Debian first though without i=
t=20
there is no good standard way for the admin to control which set(s) of=20
defaults gets activated (in what order)



[1] see Sergio's blog at=20
http://mixinet.net/stoblog/debian/20050510-cdd-dev-camp for an overview of=
=20
what happened
[2] see http://developer.skolelinux.no/~cobaco/desktop-profiles (you have t=
o=20
plug your own package whenever possible right? :), should enter Debian soon=
=20
now
=2D-=20
Cheers, cobaco (aka Bart Cornelis)
 =20
1. Encrypted mail preferred (GPG KeyID: 0x86624ABB)
2. Plain-text mail recommended since I move html and double
    format mails to a low priority folder (they're mainly spam)

--nextPart2815887.kngix2qxL9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCglzo5ihPJ4ZiSrsRAh6qAJ0V6DCIe9mk9n7I+5x7IguJrSPfdQCeK+o9
javSYjrcvaFxglQZGYfTxeY=
=ehAw
-----END PGP SIGNATURE-----

--nextPart2815887.kngix2qxL9--