On Mar 22, 2011, at 15:54, Peter Dyballa wrote:
>
> Am 22.03.2011 um 00:45 schrieb Dave Ray:
>
>> I can fix the problem by adding the appropriate variables to
>> ~/.MacOSX/environment.plist. But then I have two files to maintain,
>> /etc/bashrc and ~/.MacOSX/environment.plist. I would prefer
My version results are for bzip2 included in a clean install of MacOSX-10.6.7.
I suspect the binary compiled version is actually bzip2-1.0.6 because
clamav-0.97 configures, compiles, and installs cleanly. bzip2-1.0.5 causes a bug
report in the clamav configure.
Jeremy Huddleston wrote:
On Ma
Am 22.03.2011 um 00:45 schrieb Dave Ray:
I can fix the problem by adding the appropriate variables to
~/.MacOSX/environment.plist. But then I have two files to maintain, /
etc/bashrc and ~/.MacOSX/environment.plist. I would prefer not to
have to do that, unless that is the expected way.
On Mar 22, 2011, at 14:14, John B Brown wrote:
> Keeping change to a bare minimum is an admirable pursuit. My particular
> bugbear is the bzip2 libraries and the Apple refusal to remove the broken
> version numbers from the 'fixed' binary for bzip2. 10.6.7 claims a fix for
> both bzip2 a
Am 22.03.2011 um 17:28 schrieb Jeremy Huddleston:
So X11_Legacy shows your emacs issue still? If that's the case,
then it definitely sounds like this is a client issue and not a
server issue.
The same client, i.e., the same C and ELisp code, when linked with
libraries from Fink and /usr
Dave Ray wrote:
John B. Brown wrote:
How does MacPorts install with it's path corrections if you have no .profile or
.bash_profile? What you set in your $HOME is what sets your actually running
environment. Why would you not use your own environment setup instead of some
one size fits all Ap
John B. Brown wrote:
> How does MacPorts install with it's path corrections if you have no .profile
> or
> .bash_profile? What you set in your $HOME is what sets your actually running
> environment. Why would you not use your own environment setup instead of some
> one size fits all Apple offer
For me, the most crucial fixes are to Bzip2 and ClamAV. That Bzip2 fix has been
a bugbear for a much longer time than it should have been; the fix has been
available since before 10.6.6.
Shalom,
John B. Brown.
[j...@vcn.com]
358 High Street,
Buffalo, W
On Mar 22, 2011, at 04:56, Peter Dyballa wrote:
>
> Am 22.03.2011 um 01:06 schrieb Jeremy Huddleston:
>
>> 1) sudo rm -rf /usr/X11* /Applications/Utilities/X11.app
>> /System/LuanchAgents/org.*.startx.plist
>> 2) Install 2.2.0
>> 3) Logout
>
>
> I found only 2.2.0.1 – and it shows the effect
On Mar 22, 2011, at 04:51, Peter Dyballa wrote:
>
> Am 22.03.2011 um 01:01 schrieb Jeremy Huddleston:
>
>> which is why I told you to keep /usr/X11 from 2.6.1 if you want to use
>> X11_Legacy, so your fink and quartz-wm will resolve right ...
>
> I did save these files, but I did not understa
Yeah, we pulled in some security fixes from Freetype. The KB article is
slightly off. The version of freetype in 10.6.7 is 2.4.4 which is the same
version present in XQuartz 2.6.0 and 2.6.1. Keep in mind that XQuartz installs
to /opt/X11 whereas the Apple-provided X11 is in /usr/X11. You sho
On Tue, Mar 22, 2011 at 11:14 AM, Brian Bender
zt4q4o402-at-sneakemail.com |Xquartz-dev/Allow to me|
wrote:
> The 10.6.7 update last night supposedly fixed X11 bugs. Should I
> reinstall the XQuartz-2.6.1 package over top of it now, or leave it
> alone?
Specifically, it updated FreeType to v2.4.3
Hi all,
The 10.6.7 update last night supposedly fixed X11 bugs. Should I
reinstall the XQuartz-2.6.1 package over top of it now, or leave it
alone?
Thanks,
- Brian
___
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.o
How does MacPorts install with it's path corrections if you have no .profile or
.bash_profile? What you set in your $HOME is what sets your actually running
environment. Why would you not use your own environment setup instead of some
one size fits all Apple offering?
Shalom,
Am 22.03.2011 um 01:06 schrieb Jeremy Huddleston:
1) sudo rm -rf /usr/X11* /Applications/Utilities/X11.app /System/
LuanchAgents/org.*.startx.plist
2) Install 2.2.0
3) Logout
I found only 2.2.0.1 – and it shows the effect. And much more!
X11-2.2.0.1.pkg: X.org Release 7.2, X.Org X Server 1
Am 22.03.2011 um 01:01 schrieb Jeremy Huddleston:
which is why I told you to keep /usr/X11 from 2.6.1 if you want to
use X11_Legacy, so your fink and quartz-wm will resolve right ...
I did save these files, but I did not understand that this X11_Legacy
package is not complete and needs oth
16 matches
Mail list logo
