On Jun 27, 2011, at 21:48, Kevin Reid wrote:
> On Jun 27, 2011, at 19:36, Michael_google gmail_Gersten wrote:
>
>> Is there a good way to use macports as a non-root user for everything
>> except the install?
>>
>> Or, is there a way to limit the installation functions to a single
>> setuid prog
On Jun 27, 2011, at 19:36, Michael_google gmail_Gersten wrote:
> Is there a good way to use macports as a non-root user for everything
> except the install?
>
> Or, is there a way to limit the installation functions to a single
> setuid program?
It is possible but unsupported. You have to build
Is there a good way to use macports as a non-root user for everything
except the install?
Or, is there a way to limit the installation functions to a single
setuid program?
... something about routinely going root to compile or edit, etc,
really makes me worried about typeos.
--
Political and e
Ok, I'd like some advice here.
Qemu has some cocoa support built in. But it warns that it is not
complete, and see the mailing list archives for details.
Qemu, using core audio drivers, triggers a kernel driver problem on
PPC 10.5.8, at least on my iBook. (Seriously, I've had to turn my
machine o
Bradley Giesbrecht wrote:
>
> On Jun 27, 2011, at 10:14 AM, Bjarne D Mathiesen wrote:
>
>>
>> https://trac.macports.org/wiki/howto/AdvancedDailyAdm
>
> \${2} : install prefix ( default /macports )
>
> This is not the MacPorts default prefix. The default prefix is /opt/local.
I know tha
On Jun 27, 2011, at 10:14 AM, Bjarne D Mathiesen wrote:
> Michael_google gmail_Gersten wrote:
What is the proper way to maintain a local port?
2. Modifying an existing port.
>>>
>>> 2) keeping local patches
>>> (2) can be a bit of a pain in the ass, but has the advantage that you
Michael_google gmail_Gersten wrote:
>>> What is the proper way to maintain a local port?
>>>
>>> 2. Modifying an existing port.
>>
>> 2) keeping local patches
>> (2) can be a bit of a pain in the ass, but has the advantage that you'll
>> discover when and if the official port breaks your patch.
>>
On Mon, Jun 27, 2011 at 03:09, Michael_google gmail_Gersten
wrote:
>
> What is archive mode?
Archive mode packages the destroot before installing and then stores
this archive (as a tarball I think by default). You can then transfer
these packages to another MacPorts installation and MP will untar
>From the changelog:
83 - Port images are now stored as archives. Archive mode is now
effectively
84always on. Among other benefits, this fixes some bugs with the
handling
85of hard links installed by ports (e.g. #13601).
86
87Direct mode is no
>> What is the proper way to maintain a local port?
>>
>> 2. Modifying an existing port.
>
> 2) keeping local patches
> (2) can be a bit of a pain in the ass, but has the advantage that you'll
> discover when and if the official port breaks your patch.
>
> I've got procedures and scripts to handle
10 matches
Mail list logo