| 1 |
>> |
| 2 |
>> Personally, I'd love to see a category (or multiple categories?) |
| 3 |
>> just for software intended exclusively for Mac OS X. Might be a bit |
| 4 |
>> more difficult to swing that by the rest of the developers, though... |
| 5 |
> |
| 6 |
> This implies there should also be a separate category for packages |
| 7 |
> that are suitable for Lunix only. In the ideal world, IMO, x11-libs/ |
| 8 |
> qt should build on both platforms, behaving correctly whether it is |
| 9 |
> on MacOS or Linux; it is inelegant to require users on different |
| 10 |
> platforms to emerge different packages to get the same thing |
| 11 |
> (although for development reasons it might be reasonable to have an |
| 12 |
> x11-libs/qt-meta package that pulls in either linux-libs/qt or macos- |
| 13 |
> libs-qt as required). |
| 14 |
> |
| 15 |
|
| 16 |
The problem is that there exist a package x11-libs/qt, which already |
| 17 |
builds fine on MacOS (with installed X libs), and which is generic, and a |
| 18 |
package (apple-libs?)/qt, which uses Qt-Mac and native Aqua. |
| 19 |
As long as no Aqua exists on Linux, this is Apple only. |
| 20 |
|
| 21 |
Regards |
| 22 |
Dirk |
| 23 |
-- |
| 24 |
gentoo-osx@g.o mailing list |
Archives