Help with port/bug ticket

On 11/12/17 17:58 , Ryan Schmidt wrote: >> Bumping rules? >> I have this bug ticket open: https://trac.macports.org/ticket/55187 - where >> you were kind to make it assigned, and fixed the keywords, etc. >> >> Haven't heard anything in 2 weeks now. Is there any “protocol” how to bump >> tickets.

Questions on Apache2 + mods

Hi, Just brief before I start writing anything… If i have questions/request/suggestion for changes on a port (apache2), should I do that here (ie. discuss it first), or perhaps in the tracker->request (&/or enhancment). There are also a couple of mod_* I'm missing and would like to hear about them

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

Hi, I have some 5-6 ports that show this (gptfdisk, flac, etc.). Do you have an example how to use the cxx_stdlib_overridden.tcl, or are there any documentation to read more how to use it. Sorry, if it's obvious, but I couldn't find it. /// Since I'm using 10.7.5 with the CXX-fix

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

On 5/31/18 21:24 , Joshua Root wrote: > On 2018-6-1 03:21 , iEFdev wrote: >> Hi, >> >> I have some 5-6 ports that show this (gptfdisk, flac, etc.). Do you have >> an example how to use the cxx_stdlib_overridden.tcl, or are there any >> documentation to read m

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

On 6/1/18 0:36 , Joshua Root wrote: > On 2018-6-1 07:24 , iEFdev wrote: >> I made a quick test on flac, adding: >> >> # flac is using libstdc++ (this installation is configured to use libc++) >> configure.cxx_stdlib libstdc++ >> >> …and the rev-upgrade let

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

Sorry for the late reply. I showed up in an upgrade this morning and biult fine now. I'll add tickets for the others. Thanks... · Eric On 6/1/18 5:24 , Ryan Schmidt wrote: > On May 31, 2018, at 12:21, iEFdev wrote: > >> I have some 5-6 ports that show this (gptfdisk, flac,

CC vs assign

Hi, When I added #56618, I forgot to CC the maintainer (mojca). When modifying the ticket that CC option is gone, and all there's left is assign. I'm not really sure I feel that's up to me to do the assigning part. How should I do/proceed? - - - [OT] Of all the different mailing lists... Only

Re: CC vs assign

On 6/6/18 9:19 , Rainer Müller wrote: > Assign is the correct action to take. Otherwise someone else would just > move it from CC and assign it to the maintainer later. > > Documentation will still tell you to use CC, because the plugin that > allows reporters to use assign was only added a few wee

Help with a Portfile

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 checksum (when cloning r

Re: Help with a Portfile

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

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

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

Re: Help with a Portfile

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

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 >> temporaril

Re: Help with a Portfile

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.

Help with a Portfile (part 2)

s well then? I put the Portfiles here in a gist: https://gist.github.com/iEFdev/f3cc223c4596be6d8eebfde5622ff533 …incl the stdout of the build // The dependency Portfile is complete, and works. The other one is more like a draft, upto the “build phase”. :) Perhaps it needs some more advanced form of conf

Re: Help with a Portfile (part 2)

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)

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

Re: Help with a Portfile (part 2)

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

LaunchDaemon and startupitem

Hi, I'm thinking about LaunchDaemon. I've made a one running once a month. What's the best way to include it into a port. As a separate file moved into location, or as I've seen i some Portfiles - using “set foo [open …]” and “puts”, to create it in place. Are there any good praxises/rules to foll

Re: LaunchDaemon and startupitem

Thanks Josh! That looks interesting. Yes, keep it as a file is prob the best, but if using puts, for the example. Something like this then (based on the dbus example)? set daemon_uniquenameorg.macports.${name} startupitem.typelaunchd startupitem.create no startupitemsname

Re: LaunchDaemon and startupitem

On 1/21/19 10:44 , Joshua Root wrote: >> startupitemsnamedbus-system \ >> locationLaunchDaemons \ >> uniquename ${daemon_uniquename} \ >> plist ${daemon_uniquename}.plist > Sure, that works. You don't have to use

Q about a (new) portgroup file

Hi, While waiting on a PR and a ticket, I spent the weekend looking at file I once started with. // From an earlier convo (w Ryan): … since github.setup sets it for you; >>> An off-topic question about github.setup… There's no gitlab.setup? >>> Or can it be used by manually specifying some v

Re: Q about a (new) portgroup file

Thanks Chris, On 1/27/19 12:41 , Christopher Jones wrote: >> So, I'd like to ask… Where to put it? > > The port group code lives in the same GitHub project as the ports. See > > https://github.com/macports/macports-ports/tree/b7dbaee30cd63f197eb8d1b0db9090a5a5c948f4/_resources/port1.0/group > > N

Re: Q about a (new) portgroup file

On 1/27/19 14:21 , Christopher Jones wrote: > If you don’t think it is quite ready, but you want to start to get feedback, > then that is exactly with WIP PRs are for. Just remember to start the title > with ‘WIP” and also add the wip label to the PR. > > Chris Thanks! Ok, here it is: https://git

Re: Q about a (new) portgroup file

On 1/27/19 19:39 , Rainer Müller wrote: > On 27.01.19 14:33, Eric F (iEFdev) wrote: >> Ok, here it is: https://github.com/macports/macports-ports/pull/3510 >> Hope that was ok. At least it passed the checks. :) > FYI, Travis CI will only test changed Portfiles, as you can see o

Testing an idea

Hi, I had this idea I want to test here. When creating a Portfile and adding: maintainers - only GitHub is recognized when adding a username like “@fooBar”. One *could* cheat and use: In Portfile: maintainers{GitHost:\ @fooBar} With "port info": Maintainers: Email: GitHost: @fooBar

Re: Testing an idea

es I read back then, but a quick search now: - https://medium.com/@an0xff/gitlab-loves-github-c5ec797f7814 - https://docs.gitlab.com/ee/integration/github.html - https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/github_integration.html /Ok, I'll keep the patch (//»» <https://gist.github.

Re: Testing an idea

On 2/10/19 11:23 , Chris Jones wrote: >> Speaking of that… Are there any plans to expand to GitLab? They have a great >> function to import/mirror from GitHub, which keep the repo updated. > What do you mean by expand to gitlab?. We have > > https://github.com/macports/macports-ports/pull/3510 > >

Re: Testing an idea

On 2/10/19 14:05 , Mojca Miklavec wrote: > We do support fetching sources of various software from bitbucket and > gitlab (improved / simplified support underway; Chris mentioned > https://github.com/macports/macports-ports/pull/3510 for example), but > that's orthogonal to what you are asking. Ye

Reopening a PR.

Hi all, Tried to open a PR on GitHub, but there's no option to do so. Searched around a bit, and one place said that when adding a new commen - it would come up an option to also reopen it. But, it didn't. Any ideas? · Eric

Re: Reopening a PR.

Sorry about the noise. Chris was /really/ fast and had already fixed it. Thanks! · Eric On 9/7/19 22:24 , Eric F (iEFdev) wrote: > > Hi all, > > Tried to open a PR on GitHub, but there's no option to do so. > > Searched around a bit, and one place said that when adding a

Port variants for deps

/Evening all,/ To pass along a variant for a dependency, without having to add in when you install. How do you do that? …or is there really no other way than adding it during “port install”. One /would/ like to do: ``` depends_lib.append port:first \ port:second +fo

Re: Port variants for deps

-16 12:44 , Eric F (iEFdev) wrote: >> /Evening all,/ >> >> To pass along a variant for a dependency, without having to add in when >> you install. >> How do you do that? …or is there really no other way than adding it >> during “port

Re: Port variants for deps

On 9/16/19 23:20 , Ryan Schmidt wrote: > On Sep 15, 2019, at 22:31, Eric F (iEFdev) wrote: >> What would be better (ie good “portiquette”)… Adding subports (keeping the >> variants), or replacing variants with subports? > Provide only one way for a user to install a feature. C

Re: Port variants for deps

l xtra code added to solve it. To go back to earlier discussion… Even if the PR was closed (and I don't expect it to get reopened again), I finished it with an example of separate (sub-)subports and variands. Just wanted to finish it, exapand the idea, and see where [the code] took me. »»» <

Re: PRs now going back 18 months -- let's close the clearly dead ones

On 7/26/20 8:20 , Ryan Schmidt wrote: >> We don’t want the PR queue to start to look like the (ridiculous) ticket >> list, with dormant open tickets going back decades. >> >> Ken > > The ridiculous ticket list is similarly important. … > > Of course, if there are open tickets or PRs that are "cle

Re: port "cask" -- installing prebuilt binaries

On 8/15/20 8:48 , Lothar Haeger wrote: >> Am 15.08.2020 um 01:11 schrieb Ken Cunningham >> : >> >> so -- what would a user typing > Obviously that variant would conflict with all other variants, much like > +ruby21 conflicts with +ruby22. So the user would type > > sudo port -v install macvim +p

Re: supertuxkart non-redistributable?

Fedora, who usually are very restricted about things, have this take: > “ However, we consider that the OpenSSL library is a system library, as > defined by the GPL, *on Fedora* and therefore we are allowed to ship GPL > software that links to the OpenSSL library. …” > — > https://fedoraproject

Portfile: fetching/verifying a single file

Hi, When downloading/fetching a single (script) file from a Git repo. If I use: ``` fetch { file mkdir ${worksrcpath} system -W ${worksrcpath} "curl -qs ${master_sites}/${_file} -o ${distpath}/${distname}" } post-checksum { copy ${distpath}/${distname} ${worksrcpath} } ``` That wor

Re: Portfile: fetching/verifying a single file

On 8/29/20 5:52 , Ryan Schmidt wrote: > On Aug 28, 2020, at 21:52, Eric F wrote: >> When downloading/fetching a single (script) file from a Git repo. If I use: >> >> // ... >> >> That works, and I can verify against the checksums, etc. But is that an ok >> method? …or is there a better &/or prefer