Alexander Hansen wrote:
> Martin Costabel wrote:
>> Alexander Hansen wrote:
>> []
>>> Do we have the skilled-person-hours to pull it off, though?
>> We have a couple of more important things to do:
>>
>> For example, accept the texlive package and make a system-tex package,
>> so that the tetex mes
Martin Costabel wrote:
> Alexander Hansen wrote:
>> Martin Costabel wrote:
>>> Alexander Hansen wrote:
>>> []
Do we have the skilled-person-hours to pull it off, though?
>>> We have a couple of more important things to do:
>>>
>>> For example, accept the texlive package and make a system-tex p
Huh? What problems? I've have...
ii qt33.3.8-1028 Cross-Platform GUI application framework
ii qt3-designer 3.3.8-1028 Cross-Platform GUI application framework
ii qt3-designer-s 3.3.8-1028 Cross-Platform GUI application framework
ii qt3-doc3.3.8-1028 Cross-
Martin Costabel wrote:
> Alexander Hansen wrote:
> []
>> Do we have the skilled-person-hours to pull it off, though?
>
> We have a couple of more important things to do:
>
> For example, accept the texlive package and make a system-tex package,
> so that the tetex mess can be cleaned up once and fo
Alexander Hansen wrote:
[]
> Do we have the skilled-person-hours to pull it off, though?
We have a couple of more important things to do:
For example, accept the texlive package and make a system-tex package,
so that the tetex mess can be cleaned up once and for all;
For example, make qt3 and qt
Jack Howarth wrote:
> I got a clarification from Jeremy about the X11 support
> in MacPorts. They went through a phase when building against
> both the system and MacPorts X11 was allowed. Now everything
> must build against the MacPorts X11 or it is considered a
> packaging bug. I don't know if
I got a clarification from Jeremy about the X11 support
in MacPorts. They went through a phase when building against
both the system and MacPorts X11 was allowed. Now everything
must build against the MacPorts X11 or it is considered a
packaging bug. I don't know if anyone here wants to assume
th
As shown from the response I posted from Jeremy
Huddleston at Apple, it won't help waiting for
Xquartz on SL because all the files in Xquartz will
be relocated into /opt to survive system software
updates. This brings up the question of how we are
going to handle this relocation in the first pla
Here is the response I got from Jeremy Huddleston who does the
Xquartz releases. Note that waiting on a Xquartz release for
SL won't help since all of Xquartz's X11 files will be relocated
in /opt to allow it to survive system software updates.
Jack
ps We could take the MacPorts opti
Daniel Macks wrote:
> On Sat, Aug 29, 2009 at 09:58:06AM -0400, Alexander Hansen wrote:
>
>> This isn't any different than the usual issues we've had on 10.5, when
>> you get down to it. System updates cause regressions with respect the
>> libraries in Xquartz, and Xcode updates regress the hea
On Sat, Aug 29, 2009 at 09:58:06AM -0400, Alexander Hansen wrote:
> This isn't any different than the usual issues we've had on 10.5, when
> you get down to it. System updates cause regressions with respect the
> libraries in Xquartz, and Xcode updates regress the headers and libtool
> archives (n
Alexander Hansen wrote:
[]
> I didn't realize when I wrote my prior message that it was the _Xquartz_
> update that wasn't going to be put into release until December.
The problem appears only if xquartz-2.4.0 was installed. If no Fink
package was built against anything more recent than xquartz-2
>>
> This isn't any different than the usual issues we've had on 10.5, when
> you get down to it. System updates cause regressions with respect the
> libraries in Xquartz, and Xcode updates regress the headers and
> libtool
> archives (not to mention just clobbering them outright).
One HUGE imp
William G. Scott wrote:
> Hi folks:
>
> After upgrading, I discovered that the SL (10.6) distributed X11.app
> clobbers the X11.app v. 2.4.0 I had installed, and (unlike with 10.5.X
> point updates), there are no plans to release an X11.app update before
> ca. December. So this means users wh
William G. Scott wrote:
> Hi folks:
>
> After upgrading, I discovered that the SL (10.6) distributed X11.app
> clobbers the X11.app v. 2.4.0 I had installed, and (unlike with 10.5.X
> point updates), there are no plans to release an X11.app update before
> ca. December. So this means users wh
15 matches
Mail list logo
