Le mercredi 23 mars 2011 à 17:30 -0400, Robert Xu a écrit : > On Mar 23, 2011, at 17:28, Dexter Morgan <dmorga...@gmail.com> wrote:
> > we will face too many pbs simple question: > > > > we provide k3b ( kde apps ) trinity provide k3b ( kde3 apps ) > > Uh, no, k3b-trinity or k3b-kde3 And for configuration path, various paths in /usr/ etc ? Library name too. > > > > files are similar ( or named the same ), how users will distinguish > > No.. That's the purpose of /opt/kde3 /opt is in no way clean packaging. This is a violation of fhs ( http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES ), and a rpmlint error ( dir-or-file-in-opt ). A rpm should place stuff in /usr, unless there is a good reason. > > the version it wants? how to deal with conflicts ? > > What conflicts? We're installing in a seperate prefix. Also, the RPM > requires, provides, conflicts, etc have long been fixed, no? The whole conflicts/provides/requires were likely cleaned from our rpms, and if they are not, they should be since a regular desktop environnement should not need such provisions. We do not had conflict between gnome and kde, or lxde and xfce, so I see no reason to add them for kde and tde. They were the cause of major headaches in the past, so if a package is added, it must be clean before being uploaded. -- Michael Scherer