Re: fontforge package really old - need help with Portfile

On 2018-04-19 00:08, Ryan Schmidt wrote: > Note that there is a ticket requesting this update: > > https://trac.macports.org/ticket/43844 > > There isn't any work done there, but there is an interested developer you > could contact to collaborate. Great, are you tlking about the dev who

Re: Buiid/install stages documentation?

On 2018-4-19 01:09 , Perry E. Metzger wrote: > On Wed, 18 Apr 2018 16:14:58 +0200 Rainer Müller > wrote: >>> Maybe I should ask this a bit differently. Are there other >>> precedents for using a "foreign" packaging or build system and >>> tricking it into building stuff for

Re: Update port:openssl dependency to path:lib/libssl.dylib:openssl

On Apr 18, 2018, at 06:47, Jan Stary wrote: >>> https://github.com/macports/macports-ports/commit/607997ade7f0bd99c7a7297d7a49ae79442b705f > >>> aqua/qt5/Portfile| 2 +- >>> aqua/qt55/Portfile | 2 +- >>> aqua/qt56/Portfile | 2 +- >>>

Re: fontforge package really old - need help with Portfile

On Apr 18, 2018, at 12:36, Helmut K. C. Tessarek wrote: > I've recently found out that I need fontforge and the python bindings > for creating fonts (ForkAwesome) but the package on MacPorts is really, > really old. Note that there is a ticket requesting this update:

Re: Is it possible to specify variant as part of depends_lib?

> On Apr 18, 2018, at 7:52 PM, Edward Maros wrote: > > On 4/18/18 3:39 PM, Ryan Schmidt wrote: >> On Apr 18, 2018, at 12:39, Edward Maros wrote: >> >>> I have a package (gds) that has a build requirement on port root5 with >>> the variant +python27. >>> >>> Currently

Re: Buiid/install stages documentation?

I’ll offer my two cents. One overriding issue of package management is dependency resolution. In the case of ruby, multiple versions of a gem happily co-exist globally with applications loading compatible subsets based on its Gemfile.lock, by virtue of package dependency resolver, bundler.

Re: Is it possible to specify variant as part of depends_lib?

On Apr 18, 2018, at 12:39, Edward Maros wrote: > > I have a package (gds) that has a build requirement on port root5 with > the variant +python27. > > Currently the buildbot system will not build the gds package because it > installs the root5 package with only default variants. > > Any ideas

Is it possible to specify variant as part of depends_lib?

I have a package (gds) that has a build requirement on port root5 with the variant +python27. Currently the buildbot system will not build the gds package because it installs the root5 package with only default variants. Any ideas on how to get the variant passed (at least for the buildbot

fontforge package really old - need help with Portfile

I've recently found out that I need fontforge and the python bindings for creating fonts (ForkAwesome) but the package on MacPorts is really, really old. The project has moved from sourceforge to github and I was trying to create a new Portfile (since it doesn't have a maintainer), but I ran into

Re: Buiid/install stages documentation?

Hi, - On 18 Apr, 2018, at 15:20, Perry E. Metzger pe...@piermont.com wrote: > Maybe I should ask this a bit differently. Are there other precedents > for using a "foreign" packaging or build system and tricking it into > building stuff for macports that I could study and possibly steal >

Re: Buiid/install stages documentation?

On Wed, 18 Apr 2018 16:14:58 +0200 Rainer Müller wrote: > > Maybe I should ask this a bit differently. Are there other > > precedents for using a "foreign" packaging or build system and > > tricking it into building stuff for macports that I could study > > and possibly steal

Re: Any testers for proposed opportunistic filesystem compression?

See my comments on the thread. Yes, it is slower, but for users with fixed space, the time during activation isn't the biggest concern. On Wed, Apr 18, 2018 at 4:09 AM, Jan Stary wrote: > On Apr 12 22:58:54, ebori...@macports.org wrote: > >

Re: Buiid/install stages documentation?

On 2018-04-18 15:20, Perry E. Metzger wrote: > On Tue, 17 Apr 2018 22:33:10 -0500 Ryan Schmidt > wrote: >> On Apr 17, 2018, at 12:39, Perry E. Metzger wrote: >> >>> Just to be clear: I know what is in: >>> https://guide.macports.org/#reference.phases >>> >>> but I'm

Re: Buiid/install stages documentation?

On Tue, 17 Apr 2018 22:33:10 -0500 Ryan Schmidt wrote: > On Apr 17, 2018, at 12:39, Perry E. Metzger wrote: > > > Just to be clear: I know what is in: > > https://guide.macports.org/#reference.phases > > > > but I'm trying to figure out a bit more detail. In particular,

Re: Update port:openssl dependency to path:lib/libssl.dylib:openssl

On Apr 02 10:26:17, ryandes...@macports.org wrote: > > https://github.com/macports/macports-ports/commit/607997ade7f0bd99c7a7297d7a49ae79442b705f > > aqua/qt5/Portfile| 2 +- > > aqua/qt55/Portfile | 2 +- > > aqua/qt56/Portfile | 2 +- > >

Re: [macports-base] 01/06: fetch: Always use ${prefix}/bin/git for gitfetch

On 2018-04-18 05:37, Ryan Schmidt wrote: > > On Apr 17, 2018, at 07:33, Rainer Müller wrote: > >> On 2018-04-16 22:29, Ryan Schmidt wrote: >>> >>> On Apr 14, 2018, at 22:09, Rainer Müller wrote: >>> Rainer Müller (raimue) pushed a commit to branch vcs-fetch in repository macports-base.

Re: [macports-base] 01/06: fetch: Always use ${prefix}/bin/git for gitfetch

On Apr 17 14:33:12, rai...@macports.org wrote: > > https://lists.macports.org/pipermail/macports-dev/2018-March/037750.html > > The previous code always used /usr/bin/git, even if the git port was > installed. Only old versions of macOS got to use the latest version of > git, while recent