Re: get user's home

2017-08-08 Thread db
On 8 Aug 2017, at 02:12, Ryan Schmidt wrote: > path:-style dependencies are used when more than one port could satisfy the > dependency, in this case the development and stable versions of > bash-completion. Thanks, that cleared it up. Re ipfs, I left the startup item for the user to install

Re: get user's home

2017-08-07 Thread Ryan Schmidt
On Aug 7, 2017, at 17:01, Joshua Root wrote: > On 2017-8-8 07:55 , db wrote: >> On 7 Aug 2017, at 23:03, Joshua Root wrote: >>> Dependency specifications are documented here: >>> >> I already read that t

Re: get user's home

2017-08-07 Thread Joshua Root
On 2017-8-8 07:55 , db wrote: On 7 Aug 2017, at 23:03, Joshua Root wrote: Dependency specifications are documented here: I already read that too, but don't see why in case of docker-machine a path

Re: get user's home

2017-08-07 Thread db
On 7 Aug 2017, at 23:03, Joshua Root wrote: > Dependency specifications are documented here: > I already read that too, but don't see why in case of docker-machine a path dependency makes more sense th

Re: get user's home

2017-08-07 Thread Joshua Root
On 2017-8-8 04:43 , db wrote: On 7 Aug 2017, at 20:03, Bradley Giesbrecht wrote: On Aug 5, 2017, at 3:55 AM, db wrote: docker-machine's port, although I don't quite grasp what depends_run-append exactly does there. Depends_run-appends adds to the depends_run variable. That I knew so far,

Re: get user's home

2017-08-07 Thread db
On 7 Aug 2017, at 20:03, Bradley Giesbrecht wrote: >> On Aug 5, 2017, at 3:55 AM, db wrote: >>> docker-machine's port, although I don't quite grasp what depends_run-append >>> exactly does there. > Depends_run-appends adds to the depends_run variable. That I knew so far, but docker-machine uses

Re: get user's home

2017-08-07 Thread Bradley Giesbrecht
> On Aug 5, 2017, at 3:55 AM, db wrote: >> docker-machine's port, although I don't quite grasp what depends_run-append >> exactly does there. Depends_run-appends adds to the depends_run variable. man portfile /variable-append Regards, Bradley Giesbrecht (pixilla)

Re: get user's home

2017-08-06 Thread Umesh Singla
That cleared it up. Thanks. On Sat, Aug 5, 2017 at 2:28 AM, Joshua Root wrote: > On 2017-8-5 06:46 , Umesh Singla wrote: > >> On a side note, I didn't get this part: >> >> The user installing the port is not necessarily the one that will >> use it. >> > > Suppose a port is built on the b

Re: get user's home

2017-08-05 Thread db
On 5 Aug 2017, at 10:00, Joshua Root wrote: > I don't think there is a good way to do it if the user's home directory must > be encoded into the plist. But I suspect that is not the case, and Rainer has > mentioned a good alternative in the ticket. IPFS_PATH sets the path to ipfs' repo for file

Re: get user's home

2017-08-05 Thread Joshua Root
On 2017-8-5 07:14 , db wrote: On 4 Aug 2017, at 22:58, Joshua Root wrote: Suppose a port is built on the buildbot. The user is 'buildbot' and so the value of $user_home will be something like '/Users/buildbot'. During testing I didn't thoroughly checked that env var there. I suppose, it cou

Re: get user's home

2017-08-04 Thread db
On 4 Aug 2017, at 22:58, Joshua Root wrote: > Suppose a port is built on the buildbot. The user is 'buildbot' and so the > value of $user_home will be something like '/Users/buildbot'. During testing I didn't thoroughly checked that env var there. I suppose, it could be deleted or set to nil an

Re: get user's home

2017-08-04 Thread Bradley Giesbrecht
> On Aug 4, 2017, at 1:46 PM, Umesh Singla wrote: > > On a side note, I didn't get this part: > > The user installing the port is not necessarily the one that will use it. macOS is a multi-user system. The installed ports are largely available to any system user. — Brad

Re: get user's home

2017-08-04 Thread Joshua Root
On 2017-8-5 06:46 , Umesh Singla wrote: On a side note, I didn't get this part: The user installing the port is not necessarily the one that will use it. Suppose a port is built on the buildbot. The user is 'buildbot' and so the value of $user_home will be something like '/Users/build

Re: get user's home

2017-08-04 Thread Stephen J. Butler
For example, suppose I work in IT and someone needs ipfs on their machine. I might SSH in, run "sudo port install ipfs", and then say "All done!" But I'm not the one that will use that software, so it's not proper to encode my username anywhere as a default. On Fri, Aug 4, 2017 at 3:46 PM, Umesh S

Re: get user's home

2017-08-04 Thread Umesh Singla
On a side note, I didn't get this part: The user installing the port is not necessarily the one that will use it.

Re: get user's home

2017-08-04 Thread Stephen J. Butler
If this is a system level daemon that's being started, then it seems to me that it should be storing its data in a system level location. /opt/local/var/ipfs or /opt/local/var/lib/ipfs or /opt/local/var/spool/ipfs depending on various preferences. On Fri, Aug 4, 2017 at 2:41 PM, db wrote: > On 4

Re: get user's home

2017-08-04 Thread db
On 4 Aug 2017, at 16:05, Joshua Root wrote: > Should be in $user_home (if it could be determined, which is not guaranteed). > But why do you need it? The user installing the port is not necessarily the > one that will use it. That worked, thanks. I used it for an env var's default value in ipfs

Re: get user's home

2017-08-04 Thread Joshua Root
On 2017-8-4 22:19 , db wrote: How can I get the user's home, the flesh and blood bot's? set home$::env(HOME) righteously returns /opt/local/var/macports/home/ Should be in $user_home (if it could be determined, which is not guaranteed). But why do you need it? The user installing

get user's home

2017-08-04 Thread db
How can I get the user's home, the flesh and blood bot's? set home$::env(HOME) righteously returns /opt/local/var/macports/home/