[104383] trunk/dports/python/py-numpy/Portfile

[Eric A. Borisch]

On Mon, Mar 25, 2013 at 7:03 AM, Joshua Root <jmr at macports.org> wrote:

> > Revision: 104383
> >           https://trac.macports.org/changeset/104383
> > Author:   stromnov at macports.org
> > Date:     2013-03-24 04:29:11 -0700 (Sun, 24 Mar 2013)
> > Log Message:
> > -----------
> > py-numpy: set default gcc47 variant, add gcc48 variant
> >
> > Modified Paths:
> > --------------
> >     trunk/dports/python/py-numpy/Portfile
> >
> > Modified: trunk/dports/python/py-numpy/Portfile
> > ===================================================================
> > --- trunk/dports/python/py-numpy/Portfile     2013-03-24 11:27:23 UTC
> (rev 104382)
> > +++ trunk/dports/python/py-numpy/Portfile     2013-03-24 11:29:11 UTC
> (rev 104383)
> > @@ -7,7 +7,7 @@
> >
> >  github.setup            numpy numpy 1.6.2 v
> >  name                    py-numpy
> > -revision                1
> > +revision                2
>
> A rev bump was not warranted here. Making everyone rebuild accomplishes
> nothing; everyone who currently has the port installed will still have
> the same gcc variant selected after they upgrade.
>
> - Josh
>

I've pondered ones like this one before. Shouldn't the binary packages be
updated (and would they without the revbump)? Don't we want the binary to
match (as close as possible) what would happen if someone built from
source? And related, if someone installs (source or binary) rev1 (new
install, pre-change) today, and someone else installs (source) rev1 (if it
hadn't been bumped) new tomorrow don't we want those to match?

I understand the upgrading point, which brings up another question I've had
- should we highlight for users (especially those less interested in the
guts, and just in "does it work" and "homebrew is so much faster") in some
fashion when default variants have changed, causing their previously quick
binary upgrades into unexpected source builds?

 - Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20130325/e3c0f325/attachment.html>