[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)

Thu Mar 24 22:19:32 CET 2011

Robert Xu a écrit :
+>
+> On Mar 23, 2011, at 17:28, Dexter Morgan<dmorganec at gmail.com>  wrote:
+>
+>> On Wed, Mar 23, 2011 at 10:19 PM, Olivier Blin<mageia at blino.org>  wrote:
+>>> Dexter Morgan<dmorganec at gmail.com>  writes:
+>>>
+>>>>> I certainly don't have the web space and bandwidth resources for a
+>>>>> repository and frankly I joined Mageia as a packager precisely because I
+>>>>> thought Mageia would finally make confusing and conflicting third party
+>>>>> repos (like Mandriva has) obsolete.
+>>>>>
+>>>>>
+>>>>> We can host repositories for you, if Mageia is unwilling to accept them -
+>>>>> you could make a kde3 rpm that adds the necessary sources to use. Or, Mageia
+>>>>> could make an official kde3 repository that is disabled by default but can
+>>>>> be enabled on installer/rpmdrake. I'm not the expert at this, though :-/
+>>>>> that's mageia dev decisions.
+>>>>
+>>>> no a special repo hosted by mageia is not a good idea, we will not
+>>>> start to do repo for all that way. This need  to be external,
+>>>> independant repository.
+>>>> If you can host it this would be perfect.
+>>>
+>>> This would be a mess, like previously with Mandriva and its few
+>>> third-party repositories with various quality level, where the distro
+>>> packaging policy can't be enforced.
+>>> This is bad for end-users.
+>>>
+>>> Why not include TrinityDE in Mageia repos?
+>>> If not conflicting with KDE4, not having similar provides, and not even
+>>> installed by default, it seems ok to include it in the distro.
+>>
+>> 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
+>
+>>
+>> files are similar ( or named the same ), how users will distinguish
+>
+> No.. That's the purpose of /opt/kde3
+>
+>> 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?
+
+It might be better to use /usr/tde/kde3/ instead of /opt/kde3/ (which is 
+a bit questionable according to fs guidelines).
+(assuming of course that /usr/tde/ is used for trinity.)
+
+That way it is unquestionably linked to trinity, and can be easily 
+retired without fear of conflict when trinity migration is complete.
+Maybe the same could be done for qt3-devel requirements ?
+(Of course that would be more work for trinity people.)
+
+It is better to use trinity-kde3 for requires, as someone else suggested.
+(And similarly trinity-qt3-devel.)
+
+my 2 cents :)
+
+-- 
+André
+