> On Nov 4, 2014, at 3:55 PM, Davide Liessi wrote:
>
> Hi all.
> I have a custom MacPorts installation in /opt/macports-i386.
> Apart from the location, the only non-default option in macports.conf
> is 'build_arch i386'.
> Trying to install unzip I get a bunch of warnings like
>
> ld: warning:
Hi all.
I have a custom MacPorts installation in /opt/macports-i386.
Apart from the location, the only non-default option in macports.conf
is 'build_arch i386'.
Trying to install unzip I get a bunch of warnings like
ld: warning: in unzip.o, file was built for i386 which is not the
architecture bei
On Nov 4, 2014, at 12:49 PM, Artur Szostak wrote:
> Now I want to know the variable name that contains:
> /opt/local/var/macports/build/_Users_vagrant_repo_ports_science_detmon/detmon/work
This would be `workpath`.
vq
___
macports-users mailing list
On Nov 4, 2014, at 12:02 PM, Artur Szostak wrote:
> Is there a typo in the online guide:
> https://guide.macports.org/#reference.phases
> under section:
> 5.3.5. Extract Phase Keywords
>
> It mentions ${workdir} when talking about use_zip, but that variable does not
> seem to be available in th
Hi Gustavo,
Yes, please do not read too much into my post. I should have stated this
may not affect everyone. However, just in case, and to make things a bit
easier...I will provide an alternative method, that achieves the same
results.
Keep in mind, that my convoluted method was because I t
Hi,
Is there a typo in the online guide:
https://guide.macports.org/#reference.phases
under section:
5.3.5. Extract Phase Keywords
It mentions ${workdir} when talking about use_zip, but that variable does not
seem to be available in the post-extract phase. So is it valid during other
phases or
On Tue, Nov 4, 2014 at 12:49 PM, Artur Szostak
wrote:
> I cant seem to figure out the appropriate variable to use for the extract
> phase. Or more specifically post-extract. Anyone know this? I thought
> ${workdir} would work but its not defines during that phase.
http://guide.macports.org/#ref
On Tuesday November 04 2014 10:53:06 Ryan Schmidt wrote:
> > Can you tell me which tool is that?
>
> There's no tool. You just use the normal OS X installer program to install
> onto an external disk instead of your internal disk.
Well, for installing to an external disk you don't need special
Hi,
I cant seem to figure out the appropriate variable to use for the extract
phase. Or more specifically post-extract. Anyone know this? I thought
${workdir} would work but its not defines during that phase.
To explain a bit more: I have a tarball with a bunch of source tarballs inside.
I wan
On Nov 4, 2014, at 8:24 AM, Gustavo Seabra wrote:
>> Macs have always provided an incredibly easy way to create a bootable
>> external harddisk (or thumb drive) and boot from it, everyone who is the
>> least concerned about being able to repair or simply maintain the main boot
>> disk should m
Thanks René,
Your answer (and Dominik’s) are reassuring, and I think I’ll bit the bullet
this weekend.
Thanks a lot!
Gustavo Seabra
Em 04/11/2014, à(s) 08:48, René J.V. Bertin escreveu:
> On Tuesday November 04 2014 08:08:17 Gustavo Seabra wrote:
>
> Is this the 1st time you'll be doing a
That’s reassuring, thanks!
Gustavo Seabra
Em 04/11/2014, à(s) 08:28, Dominik Reichardt escreveu:
> Just run the installer. After the installation ran through you only need to
> fix MacPorts (migration guide).
> Don't worry about edge cases and you don't necessarily need to do a "clean"
> ins
Just run the installer. After the installation ran through you only need to fix
MacPorts (migration guide).
Don't worry about edge cases and you don't necessarily need to do a "clean"
install if you have no problems.
Dom
> Am 04.11.2014 um 12:08 schrieb Gustavo Seabra :
>
> Hi all,
>
> I've
Hi all,
I've been following this thread with great interest, and have learned a lot
here!
However, I noticed that the whole process of installing Yosemite seems a
bit convoluted, maybe even scary, for someone who is not as versed in the
peculiarities of MacOS / BSD.
So, how would you advice a p
14 matches
Mail list logo