Re: [macports-ports] branch master updated: databases/percona: Fixed percona download URL to use version_branch again. Removed $Id$ tag. Closes; #62 Closes: https://trac.macports.org/ticket/52664 Clos

> On Nov 28, 2016, at 7:42 PM, Bradley Giesbrecht wrote: > > In IRC I wasn’t sure how to read Clemens comment: "Yes, Closes: > $ticketlink, due to the length on their own lines, preferably” > > I thought maybe a single long line commit message was not preferable. That's

Re: opencv to be revbumped?

On 29 Nov 2016, at 01:44 , Marko Käning wrote: > I figure that I should have revbumped opencv2, right? I meant opencv, of course. Well, I’ll do the revbump once the install has finished successfully...

Re: Porting software that wants to build/install its own language bindings

On Mon, Nov 28, 2016 at 7:41 PM, Karl Kornel wrote: > Yeah, I was thinking about variants, but then how best to things like > Python, with its multiple versions? I could do one variant per version, > but it would be nice if I could avoid that! I have seen a number of ports

Re: [macports-ports] branch master updated: databases/percona: Fixed percona download URL to use version_branch again. Removed $Id$ tag. Closes; #62 Closes: https://trac.macports.org/ticket/52664 Clos

On 29 Nov 2016, at 01:42 , Bradley Giesbrecht wrote: > Do you literally mean the second line blank, like this: Yes, Brad, check out the relevant wiki page at https://trac.macports.org/wiki/CommitMessages and see the example! Greets, Marko

opencv to be revbumped?

Hi devs, as - the new variant ‘avx2’ has been introduced - the default port’s configure options changed - python[23] handling has changed in commit https://github.com/macports/macports-ports/commit/14a1fa8d5e1d4e07a6f2538d1779f5f42714aed3 I figure that I should have revbumped

Re: [macports-ports] branch master updated: databases/percona: Fixed percona download URL to use version_branch again. Removed $Id$ tag. Closes; #62 Closes: https://trac.macports.org/ticket/52664 Clos

> On Nov 28, 2016, at 4:20 PM, Lawrence Velázquez wrote: > > Hi, > >> On Nov 28, 2016, at 7:13 PM, Roger Ward wrote: >> >> Bradley Giesbrecht (pixilla) pushed a commit to branch master >> in repository macports-ports. >> >> >>

Re: Porting software that wants to build/install its own language bindings

On Nov 28, 2016, at 4:32 PM, Brandon Allbery wrote: > > >> On Mon, Nov 28, 2016 at 7:31 PM, A. Karl Kornel wrote: >> What makes this confusing is that additional language support is added by >> `configure` switches (like --with-python and --without-ocaml),

Re: Porting software that wants to build/install its own language bindings

On Mon, Nov 28, 2016 at 7:31 PM, A. Karl Kornel wrote: > What makes this confusing is that additional language support is added by > `configure` switches (like --with-python and --without-ocaml), so I don't > think separate Portfiles would be the best option here. I'm also not

Re: [macports-ports] branch master updated: databases/percona: Fixed percona download URL to use version_branch again. Removed $Id$ tag. Closes; #62 Closes: https://trac.macports.org/ticket/52664 Clos

Hi, > On Nov 28, 2016, at 7:13 PM, Roger Ward wrote: > > Bradley Giesbrecht (pixilla) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/2f43f23a572b62018bd0e4c0182df99f1a9bcd34 > >

Re: Build Failure: gstreamer1-gst-plugins-bad, mesa, x265

Can you please grab a sysdiagnose before rebooting? That'll be a good first step. Once I see that, I might have some questions for next time. > On Nov 28, 2016, at 15:31, Ryan Schmidt wrote: > > > On Nov 27, 2016, at 7:49 PM, David Evans wrote: > >> On 11/27/16

Re: `git describe`

> On Nov 28, 2016, at 3:28 PM, René J.V. Bertin wrote: > >> As you discovered yourself now, 'port version' of master identifies >> itself as 2.3.99 at the moment. > > Yes, and if you look at the history of the script in config that sets that > version, it apparently has

Re: `git describe`

> On Nov 28, 2016, at 7:41 AM, René J.V. Bertin wrote: > > This is moot if master is exclusively a testing area for experiments > that may never make it to a release. If it has a more usual role and > is used by those who live on the bleeding edge, then my point stands All

Re: `git describe`

FWIW, running configure in the current master/head prints "MacPorts version 2.3.99", which complies with common practice I see elsewhere ... except that here it's a hard-coded version. R.

Re: `git describe`

On 2016-11-28 11:44, René J.V. Bertin wrote: > I presume that means they merge the development branch into master > before creating the release. Maybe. I do not want to dive deep into the release workflow of other projects. > Possibly: > > %> port provides /opt/local/bin/git-release >

`git describe`

Hi, Git has a very useful feature when tags are used properly, where each commit increases a counter so that the `git describe` command returns the current release version plus a patchlevel. I use this in certain of my KF5 -devel ports but one can also imagine a MacPorts-devel (or -testing or

"catch" wrapper (commit 0ecff30a328993179b757a13830a1a5249839dd8)

Hi, Looking at upgrading my MacPorts base I noticed this tidbit in the commit 0ecff30a328993179b757a13830a1a5249839dd8 message: The new catch command > can't simply be aliased in to the slaves like we > normally do for shared commands because it uses uplevel and aliases add > an extra