Re: Online meeting next Saturday?

On Mon, 22 Oct 2018 at 22:59, Clemens Lang wrote: > On Sun, Oct 14, 2018 at 07:29:04PM +0200, Mojca Miklavec wrote: > > What do you think about another MacPorts online meeting next Saturday > > (20th) at 13:00 UTC? > > > > If you are interested in joining: > > - Do you have time? > > - Or do you

Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Hi, I've stumbled into the same issue twice in recent days, with two different ports, which is the use of clock_gettime(CLOCK_REALTIME, ); which is only available in macOS 10.12 or newer. See for instance the issue I found yesterday in xrootd. https://github.com/xrootd/xrootd/issues/846

Verify domain for github.com/macports

Hi, GitHub now supports verifying organization's domain[1], and Homebrew verified their brew.sh[2]. Should we verify ours too? [1] https://help.github.com/articles/verifying-your-organization-s-domain/ [2] https://github.com/Homebrew -- Zero smime.p7s Description: S/MIME cryptographic

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Hi, On 23/10/18 16:35, Ken Cunningham wrote: On 2018-10-23, at 8:18 AM, Chris Jones wrote: We have worked around this in a number of ports so far, and turned off some functionality in others. I use the_silver_searcher to find stuff like this, for example in the macports-ports repo: ag -i

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

On 2018-10-23, at 8:18 AM, Chris Jones wrote: > >> We have worked around this in a number of ports so far, and turned off some >> functionality in others. >> I use the_silver_searcher to find stuff like this, for example in the >> macports-ports repo: >> ag -i clock_gettime . > > Sorry, I

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

OSX sometimes doesn't provide useful features, or has issues. I love the idea of the `snowleopardfixes` port to provide and fix for Snow Leopard. I'd support expanding the concept to other missing features such as this `clock_gettime` for ports installing on OSX that doesn't provide this

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

On 2018-10-23, at 1:57 AM, Chris Jones wrote: > Hi, > > I've stumbled into the same issue twice in recent days, with two different > ports, which is the use of > > clock_gettime(CLOCK_REALTIME, ); > > which is only available in macOS 10.12 or newer. See for instance the issue I > found

Re: Merging pull requests before 72 hours

> That's one of things our existing 72-hour timeout period is for. It's not > specific to patchfiles; it's for any issue that the maintainer hasn't > responded to. Okay, thanks Ryan :)

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

We have worked around this in a number of ports so far, and turned off some functionality in others. I use the_silver_searcher to find stuff like this, for example in the macports-ports repo: ag -i clock_gettime . Sorry, I don't follow the reference to the_silver_searcher or what the

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

BTW, here is a nice clock_gettime() replacement that Jeremy wrote up: Thanks. That is a bit better than what I cooked up for xrootd. I might replace it ;) Actually, I take that back.

Re: Verify domain for github.com/macports

On 2018-10-23 12:18, Zero King wrote: > GitHub now supports verifying organization's domain[1], and Homebrew > verified their brew.sh[2]. Should we verify ours too? macports.org is now verified for the MacPorts organization. Rainer

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Yep, that is exactly what I was thinking as well. I was pondering a specific include folder like ${prefix}/include/snowleopardfixes for want of a better title for it, where these could be placed. Then we could just add that folder to the beginning of the system header search queue. (It would

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Hi, > I have been pondering a good way to make it add the header definition > properly ( ? use specific headers such as string.h injected ahead of the > system search directory and "include_next", perhaps?) and also possibly to > make each definition selectable, or at least OS-version groups

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

On 2018-10-23, at 4:23 PM, Chris Jones wrote: > > I see no reason to not just place them directly in the main MacPorts include > prefix, i.e. normally /opt/local/include. Placing them anywhere else requires > that specific folder to be included as well, which is a complication I dont > see

Re: Creating a port for non-free software

It would have to be something akin to the oracle-instantclient port, in which the user is responsible for putting the files in the correct location. This is also how FreeBSD apparently supports GAMESS. -Marcus > On Oct 23, 2018, at 7:35 PM, Chris Jones wrote: > > Hi, > > As i understand it

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Hi, > On 23 Oct 2018, at 11:26 pm, Ken Cunningham > wrote: > > Yep, that is exactly what I was thinking as well. > > I was pondering a specific include folder like > > ${prefix}/include/snowleopardfixes > > for want of a better title for it, where these could be placed. Then we could >

Creating a port for non-free software

Recently, there was a request to create a port for a software package called GAMESS [1]. After a little research, I found out that GAMESS is *not* free software [2]. Moreover, downloading GAMESS requires registration, and neither the source nor the binary can be redistributed [3]. I believe

Re: Creating a port for non-free software

Hi, As i understand it reading the links below the user has to register themselves, name and email etc., in order to get a password to allow access to the downloads. I don’t really see how this is compatible with macports, how would you integrate this into the port file ? Chris > On 24 Oct

Re: RFC: Remove old Python versions

Fred Wright 於 2018年10月22日 週一 上午3:27寫道： > > > On Sun, 21 Oct 2018, Chih-Hsuan Yen wrote: > > > I'd like to remove old Python version - python{24,25,31,32,33}. I see no > > ports depend on python{31,32,33} and no one maintains them, but those > > ports are still kept for while. Is there a reason

Re: Verify domain for github.com/macports

On Tue, Oct 23, 2018 at 08:05:21PM +0200, Rainer Müller wrote: On 2018-10-23 12:18, Zero King wrote: GitHub now supports verifying organization's domain[1], and Homebrew verified their brew.sh[2]. Should we verify ours too? macports.org is now verified for the MacPorts organization. Thanks.

Re: OT: Apple 64-bit changes

Thanks, everyone, for the discussion. I'll have to look into how it applies specifically to our app. -- Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com On Mon, Oct 22, 2018 at 8:54 PM Mark Anderson wrote: > Oh yeah, I mean CodeWeavers / WineHQ - Apple doesn't care at all. I've >