Re: Question: wip, git, ssh and permissions

[Alistair Crooks <alistaircrooks%gmail.com@localhost>]

We took great pains, fairly early on, to change all the paths in
pkgsrc to be relative ones.

This allows one to host multiple pkgsrc trees, to put things in
non-standard locations, and, in general, not to worry what is stored
elsewhere on your file systems. So you can have development trees
co-existing with the quarterly branches. I used to use a construct
like:

.if exists(${.CURDIR}/../../instance.mk)
.include "${.CURDIR}/../../instance.mk"
.endif

in my /etc/mk.conf to enable per-source-tree pkgsrc values to be set
in a file called "instance.mk" at the top level of each pkgsrc tree.

So asking "where should I put my pkgsrc tree?" isn't the right
question to ask - it limits your options unnecessarily.

Regards,
Alistair

On 25 August 2015 at 06:46, Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost> wrote:
> On 25 August 2015 at 14:40, matthew sporleder <msporleder%gmail.com@localhost> wrote:
>> pkgsrc will automatically run SU_CMD when trying to install packages.
>>
>> Another mk.conf for you:
>> SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
>
>
> Thanks. I'm aware of that.My initial point was about where to install
> pkgsrc, not the actual installation.
>