On Saturday 21 May 2011 23:29:43 Dirk Mueller wrote:
> Can I get the opinion of the other distro packagers as well please?
> Personally I was much more happy with the previous module-based layout,
> though I can cope reasonable with the current situation as well. Any other
> opinon?
Here in Arch Li
setup for qtchooser.
Also, every binary points to the latest version in Arch (e.g. python points to
python3 not python2)
However all this discussion isn't related to Arch itself: I think that binaries
with specific version takes precedence, don't they?
- Andrea Scarpino
On March
> On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
> > "I was quite clear: "qmake" must point by default to Qt 4 if Qt 4 present."
> > While qtchooser sounds like a great solution to handle this, it only adds
> > more confusion from a p
> On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
> > "I was quite clear: "qmake" must point by default to Qt 4 if Qt 4 present."
> > While qtchooser sounds like a great solution to handle this, it only adds
> > more confusion from a p
> On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
> > "I was quite clear: "qmake" must point by default to Qt 4 if Qt 4 present."
> > While qtchooser sounds like a great solution to handle this, it only adds
> > more confusion from a p
---
>
> (Updated March 29, 2013, 1:09 a.m.)
>
>
> Review request for Build System, kdelibs, David Faure, Alexander Neundorf,
> and Andrea Scarpino.
>
>
> Description
> ---
>
> Recently ArchLinux decided to ship Qt5 and they did so by making qmak
