Default Program | File Association

[Alexander Larsson]

On Wed, 2008-01-30 at 12:49 +0100, David Faure wrote:
> This is the advantage of the InitialPreference solution: it works out
> of the box.
> 
> > > This problem is solved. What is not solved is the default order, when NO user-configuration exists,
> > > but it was pointed out that the default order is desktop-dependent anyway, so the implementation
> > > can stay desktop-dependent. I just don't want that installing a (gnome) applications means
> > > that some script will automatically change defaults.list... The app itself can do it if the user clicks
> > > "yes make this the preferred app", at runtime, then it's okay. But not at "make install" / apt-get / rpm time.
> > 
> > If KDE will start to use defaults.list, the OpenSUSE defaults.list magic
> > has to be redone.
> 
> Either that, or OpenSUSE should provide no defaults.list at all....
> OK this is not going to work in a backwards-compatible manner, I can see that now.
> We are changing the meaning of defaults.list from "the system/distro defaults (possibly modified by user)"
> to "the sysadmin or user preferences".
> 
> I think we should separate the two. How about we keep defaults.list for defaults, as the name indicates
> (in fact those would keep being the gnome defaults and wouldn't be read by kde), and we use a new name, like 
> applicationpreferences.list for the sysadmin & user preferences (that apply to all freedesktop implementations
> reading this soon-standardized file)?

I like the idea, but the filename is a bit long. I can't think of a
really good short one though. "custom.assoc"?