Am 08.09.2014 um 13:44 schrieb Jerome Leclanche: > I don't think planning in advance for qt6 makes any sense. I'd rather > just use /usr/share/lxqt as well; there's no logical reason why we > should be co-installable between qt4 and qt5. If for some crazy reason > a distro requires that, they can patch lxqt. > J. Leclanche No lxqt developer but downstream packager, but it sounds crazy to only make distinction on translations and to put them into separate folders. How is that easier to debug? Please only install it to /usr/share/$name, that is standard convention. If a distro is not ok with that, they are free to change this.
Also if the use case is parallel installation, that's not possible. What about all the other libraries, binaries and other ressources like icons and such that also need renaming? > > > 2014-09-08 13:38 GMT+02:00 Luís Pereira <luis.artur.pere...@gmail.com>: >> On Mon, Sep 8, 2014 at 3:08 AM, PCMan <pcman...@gmail.com> wrote: >>> Should we unify this by installing all data files of every component >>> to /usr/share/lxqt-qt5 when compiled with Qt5? Or just install >>> everything to /usr/share/lxqt for both Qt4 and Qt5? >> I'm in favor of installing it to different places. >> No clashes in the paths will lead to easier bug fixing in the qt4 version. >> We can have Qt4 and Qt5 itself co-installed. That's done at the >> packaging level, of course. In our case, with a small team, it's >> better to do it at the devel level IMO. >> >>> Luis seems to prefer using different data dirs for Qt4 and Qt5 builds. >>> But if we're going to do this, then every components need to be fixed >>> for the change. Personally I'm fond of using just /usr/share/lxqt >>> since the -qt5 suffix looks redundant, but maybe using a different dir >>> is better since we'll encounter the same issue when Qt 6 is released. >>> We'll have Qt 5/6 support then. >>> Any comments? If there're no objections, I think we can update every >>> component and install their data to /usr/share/lxqt-qt5. >> I can work on that. >> I will be a lot of boring boring boring work..... but I think it's >> worth it. The qt4 will be in good shape and it will be a lot easier to >> fix bugs. >> That means that the 0.8 release will be delayed. But it also means a >> better release. >> >> -- >> Luís Pereira >> >> ------------------------------------------------------------------------------ >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> _______________________________________________ >> Lxde-list mailing list >> Lxde-list@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/lxde-list > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Lxde-list mailing list > Lxde-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxde-list ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
