Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-02-04 Thread Ryan Schmidt
> On Feb 4, 2021, at 09:11, janos...@mailbox.org wrote: > > >> Am 08.01.2021 um 15:50 schrieb Ryan Schmidt: >> >> On Jan 7, 2021, at 16:26, Andrew Udvare wrote: >> >>> Sometimes the release tarball will come with the submodule source >>>

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-02-04 Thread Janosch Peters via macports-users
> Am 08.01.2021 um 15:50 schrieb Ryan Schmidt : > > On Jan 7, 2021, at 16:26, Andrew Udvare wrote: > >> Sometimes the release tarball will come with the submodule source >> https://github.com/macports/macports-ports/pull/9612#issuecomment-756376258 >> but this probably depends on the

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-01-08 Thread Ryan Schmidt
On Jan 7, 2021, at 16:26, Andrew Udvare wrote: > Sometimes the release tarball will come with the submodule source > https://github.com/macports/macports-ports/pull/9612#issuecomment-756376258 > but this probably depends on the project. If a release tarball doesn't come with everything

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-01-07 Thread Andrew Udvare
Sometimes the release tarball will come with the submodule source https://github.com/macports/macports-ports/pull/9612#issuecomment-756376258 but this probably depends on the project. On Thu, Jan 7, 2021, 07:09 wrote: > > Just some comments on the port: > > Line 13 (name) is not necessary

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-01-07 Thread Andrew Udvare
> On 2021-01-07, at 07:09, janos...@mailbox.org wrote: > > Your comment about the git submodules is a bit surprising to me because I got > that part straight from the macports guide: > https://guide.macports.org/index.html#reference.portgroup.github.submodule. > So is fetching the submodule

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-01-07 Thread Janosch Peters via macports-users
> Just some comments on the port: > > Line 13 (name) is not necessary because github.setup sets the name (second > argument). > > Does the build {} step actually download deps with Carthage? (I am fairly > certain it does). This should be avoided even if it is difficult. If Carthage > is

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2021-01-01 Thread Janosch Peters via macports-users
> Am 31.12.2020 um 19:41 schrieb Ryan Schmidt : > > On Dec 31, 2020, at 09:49, Janosch Peters wrote: > >> I think the home folder of the macports user should be owned by macports, no? > > No, it is intentional that ports cannot write to that home directory. We do > not want it to fill up

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2020-12-31 Thread Ryan Schmidt
On Dec 31, 2020, at 09:49, Janosch Peters wrote: > I am currently preparing a port file for the new port MacPass [1]. Installing > and building works fine, but I do get some warnings because a tool preparing > the build called carthage wants to create a file in >

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2020-12-31 Thread Andrew Udvare
> On 2020-12-31, at 10:49, Janosch Peters via macports-users > wrote: > > [1] > https://github.com/Janosch/macports-ports/blob/new-port-macpass/security/MacPass/Portfile Just some comments on the port: Line 13 (name) is not necessary because github.setup sets the name (second argument).