Forgot to send it to the list. Again!
On Jan 23, 2008 10:17 PM, James Sumners <[EMAIL PROTECTED]> wrote:
> Thanks for the suggestions. I have successfully built x86 binaries of
> TeXmacs, patched to depend on texlive ;), and texlive.
>
>
> On Jan 23, 2008 5:14 PM, Ryan Schmidt <[EMAIL PROTECTED]>
On 1/23/08, Michael Thon <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 22, 2008, at 5:28 PM, Matt Scilipoti wrote:
> It would be nice if we listed which apps are tested. I expect this
> would go in http://ncbi_tools.darwinports.com/ and possibly
> the
> portfile? It looks like we don't have access to a
On Jan 23, 2008 4:21 PM, James Sumners wrote:
On Jan 23, 2008, at 15:06, Chris Pickel wrote:
On 23 Jan, 2008, at 12:34, James Sumners wrote:
I just upgraded from a PowerBook to a MacBook Pro. The migration
assistant tool kept my old macports system intact. I can still
run all
of the ports
James Sumners wrote:
On Jan 23, 2008 4:21 PM, James Sumners <[EMAIL PROTECTED]> wrote:
I was concerned about configuration files outside of /opt/local. But
now that I think about it, even if there are any, the Intel port won't
have a different configuration than the PPC one. So that could
probab
Forgot to include the list.
*grumble*
On Jan 23, 2008 4:21 PM, James Sumners <[EMAIL PROTECTED]> wrote:
> I was concerned about configuration files outside of /opt/local. But
> now that I think about it, even if there are any, the Intel port won't
> have a different configuration than the PPC one
On 23 Jan, 2008, at 12:34, James Sumners wrote:
I just upgraded from a PowerBook to a MacBook Pro. The migration
assistant tool kept my old macports system intact. I can still run all
of the ports I had installed; particularly, I can still use TeXmacs
and teTeX. However, I had built all of my por
James> I just upgraded from a PowerBook to a MacBook Pro. The migration
James> assistant tool kept my old macports system intact
James> So, is there any way I can "jail" a new installation of macports?
James> If I can build everything successfully, I want to be able to
Jam
I just upgraded from a PowerBook to a MacBook Pro. The migration
assistant tool kept my old macports system intact. I can still run all
of the ports I had installed; particularly, I can still use TeXmacs
and teTeX. However, I had built all of my ports as PPC binaries, so
they are running via Rosett
>On Jan 7, 2008, at 12:49, Jay Chandler wrote:
>
>> [EMAIL PROTECTED] sudo port install ntop
>> ---> Building ntop with target all
>> Error: Target org.macports.build returned: shell command " cd "/opt/
>> local/var/macports/build/
>> _opt_local_var_macports_sources_rsync.macports.org_release_port
