Re: Help with a Portfile (part 2)

2019-01-16 Thread Eric F (iEFdev)
On 1/16/19 23:11 , Ryan Schmidt wrote: >> For the maintainer… The old 'libgeoip' was pixilla. I sent him an email >> asking if he wanted this one as well, but haven't heard anything. I guess >> nomaintainer is better, unless I should be in there. It's ok. > pixilla hasn't been seen in awhile. We

Re: Help with a Portfile (part 2)

2019-01-16 Thread Ryan Schmidt
On Jan 16, 2019, at 14:03, Eric F (iEFdev) wrote: > On 1/16/19 19:22 , Ryan Schmidt wrote: >> On Jan 15, 2019, at 15:55, Eric F (iEFdev) wrote: >> >>> It's a 2 part install. C lib (dependency) + a module. >>> - >>> https://github.com/maxmind/libmaxminddb/ >> I tried to build this Portfile

Re: Help with a Portfile (part 2)

2019-01-16 Thread Eric F (iEFdev)
On 1/16/19 19:22 , Ryan Schmidt wrote: > On Jan 15, 2019, at 15:55, Eric F (iEFdev) wrote: >> It's a 2 part install. C lib (dependency) + a module. >> - https://github.com/maxmind/libmaxminddb/ > I tried to build this Portfile and found that in the libtap directory, the > build system is not

Re: Help with a Portfile (part 2)

2019-01-16 Thread Ryan Schmidt
On Jan 15, 2019, at 15:55, Eric F (iEFdev) wrote: > It's a 2 part install. C lib (dependency) + a module. > - https://github.com/maxmind/libmaxminddb/ I tried to build this Portfile and found that in the libtap directory, the build system is not using the compiler nor flags that MacPorts

Re: Help with a Portfile (part 2)

2019-01-15 Thread Eric F (iEFdev)
Thanks for the quick reply… On 1/16/19 0:35 , Ryan Schmidt wrote: > Sounds like apxs doesn't like the -arch flag, so don't pass that to it. Maybe > using "-Wl,-arch,x86_64" instead of "-arch x86_64" is what you need. Or maybe > you don't need an -arch flag at all. Been doing some trial'n'error h

Re: Help with a Portfile (part 2)

2019-01-15 Thread Ryan Schmidt
On Jan 15, 2019, at 15:55, Eric F (iEFdev) wrote: > Thanks for all the help with last one. 👍 > > Now I'm doing the other (last) one(s), and I'm not really sure how to do this. > > It's a 2 part install. C lib (dependency) + a module. > - https://github.com/maxmind/libmaxminddb/ > - ht

Help with a Portfile (part 2)

2019-01-15 Thread Eric F (iEFdev)
Thanks for all the help with last one. 👍 Now I'm doing the other (last) one(s), and I'm not really sure how to do this. It's a 2 part install. C lib (dependency) + a module. - https://github.com/maxmind/libmaxminddb/ - https://github.com/maxmind/mod_maxminddb/ The C lib builds and instal

Re: Help with a Portfile

2019-01-15 Thread Eric F (iEFdev)
Thanks Ken… It was something like that I had in mind - putting curl/openssl in a separate folder. I'm all for #51516 // …and that is also how the FAQ describes it (FAQ#syslibs ) :) > Keep your wits about you when updating the bootstrap installation.

Re: Help with a Portfile

2019-01-14 Thread Eric F (iEFdev)
On 1/15/19 7:22 , Ryan Schmidt wrote: > On Jan 15, 2019, at 00:18, iEFdev wrote: >>> You cannot fetch from GitHub using the curl bundled with a macOS version >>> that old. >> Would it be possible to link around the problem in any way, if not just >> temporarily? Just replace curl with a newer did

Re: Help with a Portfile

2019-01-14 Thread Ken Cunningham
It is rather difficult to install libcurl with all it’s dependencies and certificates and keep it up to date with current security outside of Macports. I suggest you use the method outlined in the referenced ticket

Re: Help with a Portfile

2019-01-14 Thread Joshua Root
On 2019-1-15 17:18 , iEFdev wrote: > When I run “port fetch” - all I see is port running tclsh5.8... no curl. It uses libcurl. - Josh

Re: Help with a Portfile

2019-01-14 Thread Ryan Schmidt
On Jan 15, 2019, at 00:18, iEFdev wrote: >> You cannot fetch from GitHub using the curl bundled with a macOS version >> that old. > > Would it be possible to link around the problem in any way, if not just > temporarily? Just replace curl with a newer did'n't work. Yes, you can build MacPor

Re: Help with a Portfile

2019-01-14 Thread iEFdev
On 1/14/19 7:21 , Joshua Root wrote: > So, fetching and patching work fine for me with your Portfile.fetch.git > after removing the fetch.type line and setting the correct checksums. > > You should set an appropriate version though (hashes are not suitable > because they change pseudorandomly rathe

Re: Help with a Portfile

2019-01-14 Thread Ryan Schmidt
On Jan 13, 2019, at 21:04, iEFdev wrote: > That one will clone… but, it won't create a tarball if I skip the fetch > part.. And there's some really odd naming thing going on. The odd naming is just how GitHub works. The github portgroup handles all the details of that for you; you don't need

Re: Help with a Portfile

2019-01-13 Thread Joshua Root
On 2019-1-14 17:03 , iEFdev wrote: > Hi Josh, > > Thanks for looking at it.  :+1: > > I put the files here in a tmp branch of my macports-ports fork: > https://github.com/iEFdev/macports-ports/tree/4josh/www/libapache2_mod_fastcgi So, fetching and patching work fine for me with your Portfile.fet

Re: Help with a Portfile

2019-01-13 Thread iEFdev
Hi Josh, Thanks for looking at it. :+1: I put the files here in a tmp branch of my macports-ports fork: https://github.com/iEFdev/macports-ports/tree/4josh/www/libapache2_mod_fastcgi Well if it works for you, just like that - I guess that SSL-error is the bad one then? · Eric On 1/14/19 6:10

Re: Help with a Portfile

2019-01-13 Thread Joshua Root
On 2019-1-14 14:04 , iEFdev wrote: > On 1/14/19 0:50 , Joshua Root wrote: >> GitHub will generate a tarball for any commit you name, so there's no >> need to use fetch.type git in this case. > > // https://github.com/ByteInternet/libapache-mod-fastcgi/ > > github.setupByteInternet libapac

Re: Help with a Portfile

2019-01-13 Thread iEFdev
Hi Mojca and Josh, On 1/13/19 15:11 , Mojca Miklavec wrote: >> But maybe one could take one of the releases, and create an additional patch >> from the last commit - just to get up to date? I dont' think it's that many >> commits behind. :) > This is of course also possible, it depends on the i

Re: Help with a Portfile

2019-01-13 Thread Joshua Root
On 2019-1-14 01:11 , Mojca Miklavec wrote: > On Sun, 13 Jan 2019 at 14:32, iEFdev wrote: >> >> there is that other thing - that the commit I used is the last one made, and >> it's ≈ 2 years newer than last release. > > This is often a perfectly valid usecase for fetching the source from > git. Yo

Re: Help with a Portfile

2019-01-13 Thread Mojca Miklavec
Dear Eric, On Sun, 13 Jan 2019 at 14:32, iEFdev wrote: > > there is that other thing - that the commit I used is the last one made, and > it's ≈ 2 years newer than last release. (Intermediate comment: since you are probably not packaging some proprietary software, it could be easier to explain t

Re: Help with a Portfile

2019-01-13 Thread iEFdev
Hi Mojca, Thank you so much for your reply and help… On 1/13/19 12:27 , Mojca Miklavec wrote: > When you use github.setup, a tarball is fetched directly from the > GitHub server, without resorting to git in any way, and works as if > you fetched the sources from elsewhere. > > When you use git di

Re: Help with a Portfile

2019-01-13 Thread Mojca Miklavec
Dear Eric, On Sun, 13 Jan 2019 at 11:04, iEFdev wrote: > > I'd like to get some help with a Portfile, and have a couple of questions. > > 1: When using git.setup, with a commit as the 3'rd var, like: github.setup > Foo Bar a1b2c3d4 > > I didn't get it to work

Help with a Portfile

2019-01-13 Thread iEFdev
Hi, I'd like to get some help with a Portfile, and have a couple of questions. 1: When using git.setup, with a commit as the 3'rd var, like: github.setup Foo Bar a1b2c3d4 I didn't get it to work (download), but I could use it with: fetch.type git How does that work with checksu