On Sun, Oct 10, 2010 at 1:44 AM, Ryan Schmidt wrote:
> Now, hold on. Putting an entry into /etc/paths.d and /etc/manpaths.d
> *appends* to those paths; it does not prepend. In this case, is it a problem
> to just use /opt/local/bin, /opt/local/share/man, /opt/local/share/info as
> you've been d
On Sun, Oct 10, 2010 at 6:59 AM, John B Brown wrote:
> After I sent the log I attempted the command without the 'full' and
> it resumed with staging python26, installed it, and gave the advice
That "full" appended to texlive means nothing and gives an error on a
sane system as there's no "
On Oct 9, 2010, at 23:44, John B Brown wrote:
> Here's the log, below the quote.
>
> On 10/9/10 7:21 PM, Ryan Schmidt wrote:
>> On Oct 9, 2010, at 19:35, John B Brown wrote:
>>
>>> Log for python26 is at:
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_
On 10/9/10 7:21 PM, Ryan Schmidt wrote:
On Oct 9, 2010, at 19:35, John B Brown wrote:
Log for python26 is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python26/main.log
We will need to see what's in that log file before we can know w
Dear Folk,
Here's the log, below the quote.
On 10/9/10 7:21 PM, Ryan Schmidt wrote:
On Oct 9, 2010, at 19:35, John B Brown wrote:
Log for python26 is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python26/main.log
We will nee
On Oct 9, 2010, at 19:35, John B Brown wrote:
> Log for python26 is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python26/main.log
We will need to see what's in that log file before we can know what went wrong.
__
So, good timing on this request since we will be updating to TeXLive
2010 soon and can roll this into that change.
It may also tie in nicely with something else I was considering doing
with the texlive ports. Currently texlive-bin builds all the binaries
for everything and installs them into $pref
Dear Folk,
The error message:
---> Fetching python26
---> Attempting to fetch Python-2.6.6.tar.bz2 from
http://distfiles.macports.org/python26
---> Verifying checksum(s) for python26
---> Extracting python26
---> Applying patches to python26
---> Configuring python26
---> Buildi
>>> .Ah. Then /usr/texbin is not the bin directory, it's the prefix. So
>>> you'd really have /usr/texbin/bin being a symlink to wherever the TeX
>>> binaries are, and /usr/texbin/man (or perhaps more correctly
>>> /usr/texbin/share/man) for the manpages, /usr/texbin/info (or perhaps
>>> /u
On Oct 9, 2010, at 18:54, Faisal Moledina wrote:
>>> Man files are ultimately located at /usr/texbin/man.
>>
>> .Ah. Then /usr/texbin is not the bin directory, it's the prefix. So
>> you'd really have /usr/texbin/bin being a symlink to wherever the TeX
>> binaries are, and /usr/texbin/man
>> Man files are ultimately located at /usr/texbin/man.
>
> .Ah. Then /usr/texbin is not the bin directory, it's the prefix. So you'd
> really have /usr/texbin/bin being a symlink to wherever the TeX binaries are,
> and /usr/texbin/man (or perhaps more correctly /usr/texbin/share/man) for the
On Oct 9, 2010, at 18:24, Faisal Moledina wrote:
> On Sat, Oct 9, 2010 at 5:53 PM, Ryan Schmidt wrote:
>>
>> On Oct 9, 2010, at 16:13, Faisal Moledina wrote:
>>
>>> It would work much better if the link was
>>> /usr/texbin -> /opt/local/libexec/texlive/texbin as you suggest, Ryan.
>>> It would
On Sat, Oct 9, 2010 at 5:53 PM, Ryan Schmidt wrote:
>
> On Oct 9, 2010, at 16:13, Faisal Moledina wrote:
>
>> It would work much better if the link was
>> /usr/texbin -> /opt/local/libexec/texlive/texbin as you suggest, Ryan.
>> It would certainly be most efficient if it were done at the port
>> i
On Oct 9, 2010, at 16:00, Uli Wienands wrote:
> I have been trying to update my MacPorts installation by running "sudo port
> -d selfupdate". It fails with the following message:
>
> .
> .
> .
> ===> making install in doc
> /usr/bin/install -c -d -o root -g 501 -m 755 /opt/local
> /usr/bin/inst
On 2010-10-09 23:02 , Uli Wienands wrote:
> ===> making install in doc
> /usr/bin/install -c -d -o root -g 501 -m 755 /opt/local
> /usr/bin/install -c -d -o root -g 501 -m 755 /opt/local/etc/macports
> cat prefix.mtree | /usr/sbin/mtree -U -e -p /opt/local > /dev/null
> mtree: line 6: unknown group
On 2010-10-09 22:12 , James Berry wrote:
> You can just substitute the pseudo-port "requested" for installed above. Do
> get a list of the requested ports:
>
> port echo requested
>
> To upgrade only requested ports:
>
> port -f upgrade requested
>
> Hope that helps.
Note that thi
On Oct 9, 2010, at 16:13, Faisal Moledina wrote:
> It would work much better if the link was
> /usr/texbin -> /opt/local/libexec/texlive/texbin as you suggest, Ryan.
> It would certainly be most efficient if it were done at the port
> install level so I'll go ahead and request a modification. I r
>> Note that doing this doesn't alter anything in /opt/local. It just
>> sets up links in /usr/texbin to the appropriate location. The main
>> disadvantage that I see is that because MacPorts installs TeXLive
>> binaries in /opt/local/bin, when this TeX distribution is selected,
>> /usr/texbin woul
Aargh, I forgot to mention: This is on Mac OS X 10.4.11 Tiger,. PPC
G4 system. Trying to update to MacPorts 1.9.1.
Dear all,
I have been trying to update my MacPorts installation by running
"sudo port -d selfupdate". It fails with the following message:
.
.
.
===> making install in doc
/us
Dear all,
I have been trying to update my MacPorts installation by running
"sudo port -d selfupdate". It fails with the following message:
.
.
.
===> making install in doc
/usr/bin/install -c -d -o root -g 501 -m 755 /opt/local
/usr/bin/install -c -d -o root -g 501 -m 755 /opt/local/etc/macpo
On Oct 9, 2010, at 12:01, Bradley Giesbrecht wrote:
> I'm working on a portfile for thrift.
>
> http://incubator.apache.org/thrift/
>
> At the end of configure I see this:
>
> Building C++ Library . : yes
> Building Java Library : yes
> Building C# Library .. : no
> Bui
On Oct 8, 2010, at 13:53, Faisal Moledina wrote:
> Note that doing this doesn't alter anything in /opt/local. It just
> sets up links in /usr/texbin to the appropriate location. The main
> disadvantage that I see is that because MacPorts installs TeXLive
> binaries in /opt/local/bin, when this Te
On Oct 8, 2010, at 12:38, Mark Johnson wrote:
> Recently my old PPC PowerBook was replaced by a new Intel MacBook. Our IY
> department copied everything from the old machine to the new one.
>
> Now I find that none of the ports work and they are interfering with
> installation of new software.
Bradley,
On Oct 9, 2010, at 12:42 PM, Bradley Giesbrecht wrote:
>
> On Oct 9, 2010, at 12:19 PM, Andrea D'Amore wrote:
>
>> On Fri, Oct 8, 2010 at 7:38 PM, Mark Johnson wrote:
>>> How can I get rid of the old MacPorts or replace it with one compatible
>>> with my new machine?
>>> I can't run
On Sat, Oct 9, 2010 at 3:44 PM, Andrea D'Amore wrote:
> On Fri, Oct 8, 2010 at 8:53 PM, Faisal Moledina
> wrote:
>>The main
>> disadvantage that I see is that because MacPorts installs TeXLive
>> binaries in /opt/local/bin, when this TeX distribution is selected,
>> /usr/texbin would link to /opt
On Oct 9, 2010, at 12:19 PM, Andrea D'Amore wrote:
On Fri, Oct 8, 2010 at 7:38 PM, Mark Johnson
wrote:
How can I get rid of the old MacPorts or replace it with one
compatible with my new machine?
I can't run sudo port -f uninstall installed because the port
command does not work.
You ca
On Fri, Oct 8, 2010 at 8:53 PM, Faisal Moledina
wrote:
> I
> decided to help update the postflight script to link to MacPorts
> TeXLive ports, called MacPorts-TeXLive. I've pasted the relevant
> portion of the postflight script at http://pastie.org/1208204 and I
> was wondering if other MacTeX use
On Fri, Oct 8, 2010 at 7:38 PM, Mark Johnson wrote:
> How can I get rid of the old MacPorts or replace it with one compatible with
> my new machine?
> I can't run sudo port -f uninstall installed because the port command does
> not work.
You can install macports from latest dmg and get a list o
I'm working on a portfile for thrift.
http://incubator.apache.org/thrift/
At the end of configure I see this:
Building C++ Library . : yes
Building Java Library : yes
Building C# Library .. : no
Building Python Library .. : yes
Building Ruby Library : yes
B
On Oct 9, 2010, at 8:29 AM, Rainer Müller wrote:
>
> On 10/09/2010 01:55 PM, Bradley Giesbrecht wrote:
>> On Oct 9, 2010, at 3:17 AM, Rainer Müller wrote:
>>> 'port sync' or 'port selfupdate' overwrites any local changes. You
>>> should use a local ports tree [1] to avoid that.
>>
>> Would changi
On 10/09/2010 01:55 PM, Bradley Giesbrecht wrote:
> On Oct 9, 2010, at 3:17 AM, Rainer Müller wrote:
>> 'port sync' or 'port selfupdate' overwrites any local changes. You
>> should use a local ports tree [1] to avoid that.
>
> Would changing from rsync to svn also be a good choice?
It depends. A
On Oct 9, 2010, at 3:17 AM, Rainer Müller wrote:
On 2010-10-08 20:24 , Bill Christensen wrote:
I went back to double check my changes in the Mailman portfile and
they
weren't there. After entering them again - and removing the
original
"--with-mail-gid=${mmgroup}" which I had missed last
On 2010-10-08 20:24 , Bill Christensen wrote:
> I went back to double check my changes in the Mailman portfile and they
> weren't there. After entering them again - and removing the original
> "--with-mail-gid=${mmgroup}" which I had missed last time - everything
> appears to be working correctl
33 matches
Mail list logo
