On Aug 11, 2014, at 12:39 PM, Sean Farley wrote:
Ryan Schmidt writes:
Anyone who had the previous file, including our automated systems, will now
encounter a checksum mismatch. To fix this please follow the recipe for
stealth updates:
Hi,
I would like to do a massive commit with changes in perl modules.
I attached a patch to
https://trac.macports.org/ticket/43480
two days ago, but it is no longer suitable as such out-of-the-box
since there were a bunch of changes in perl modules (including
changing exactly the files that
On Aug 12, 2014, at 5:25 AM, c...@macports.org wrote:
Revision
123673
Author
c...@macports.org
Date
2014-08-12 03:25:35 -0700 (Tue, 12 Aug 2014)
Log Message
base: Add port reload, closes #36054, patch from #42487
Thanks!
--- trunk/base/src/port1.0/portreload.tcl
Hey,
The file name line should be removed (here and everywhere else, really) and
the standard MacPorts modeline inserted instead of this very short one.
I agree, r123675.
+# Copyright (c) 2007, 2009, 2011 The MacPorts Project
+# Copyright (c) 2007 James D. Berry
I think we just need
Hi,
Of course, a sure fire approach would be to see if Berry would be
willing to assign any copyright interest he might have in the code
to The MacPorts Project.
That might be the case for US jurisdictions, but not for the EU. For
example, as a German citizen, I cannot assign my copyright –
On Aug 12, 2014, at 4:15 AM, Mojca Miklavec wrote:
Hi,
I would like to do a massive commit with changes in perl modules.
I attached a patch to
https://trac.macports.org/ticket/43480
two days ago, but it is no longer suitable as such out-of-the-box
since there were a bunch of changes
On 8/12/14 5:04 AM, Clemens Lang wrote:
Hi,
Of course, a sure fire approach would be to see if Berry would be
willing to assign any copyright interest he might have in the code
to The MacPorts Project.
That might be the case for US jurisdictions, but not for the EU. For
example, as a German
On 8/12/14 5:34 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 4:15 AM, Mojca Miklavec wrote:
Hi,
I would like to do a massive commit with changes in perl modules.
I attached a patch to
https://trac.macports.org/ticket/43480
two days ago, but it is no longer suitable as such out-of-the-box
On 2014-8-12 22:47 , David Evans wrote:
On 8/12/14 5:04 AM, Clemens Lang wrote:
Hi,
Of course, a sure fire approach would be to see if Berry would be
willing to assign any copyright interest he might have in the code
to The MacPorts Project.
That might be the case for US jurisdictions, but
Hi,
Condition number 1 in the BSD license is that the copyright notices must
be preserved. If there's any doubt about whether some code you have
copied is sufficiently large and/or creative to be subject to copyright,
assume it is and preserve the notices. That's not an onerous task.
you're
On Tue, Aug 12, 2014 at 3:02 PM, David Evans wrote:
On 8/12/14 5:34 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 4:15 AM, Mojca Miklavec wrote:
Hi,
I would like to do a massive commit with changes in perl modules.
I attached a patch to
https://trac.macports.org/ticket/43480
two days
On Aug 12, 2014, at 4:01 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 11, 2014, at 12:39 PM, Sean Farley wrote:
Anyone who had the previous file, including our automated systems, will now
encounter a checksum mismatch. To fix this please follow the recipe for
stealth updates:
On Aug 12, 2014, at 10:15 AM, Mojca Miklavec mo...@macports.org wrote:
Other than that I can definitely create a new branch to simplify
testing and add the same patch to all perl versions. But the request
to wait with updates a bit (unless it's really really really needed)
still stands.
you
On 8/12/14 7:15 AM, Mojca Miklavec wrote:
On Tue, Aug 12, 2014 at 3:02 PM, David Evans wrote:
On 8/12/14 5:34 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 4:15 AM, Mojca Miklavec wrote:
Hi,
I would like to do a massive commit with changes in perl modules.
I attached a patch to
On Tue, Aug 12, 2014 at 4:30 PM, Daniel J. Luke wrote:
On Aug 12, 2014, at 10:15 AM, Mojca Miklavec wrote:
Other than that I can definitely create a new branch to simplify
testing and add the same patch to all perl versions. But the request
to wait with updates a bit (unless it's really
On Tue, Aug 12, 2014 at 4:43 PM, David Evans wrote:
I'd be happy to help with this. It's true that many ports are outdated
version-wise (even ones that have already been ported to p5.20)
and my recent experience suggests that many need updated
dependencies as well.
To make things
On Aug 12, 2014, at 9:26 AM, Daniel J. Luke wrote:
On Aug 12, 2014, at 4:01 AM, Ryan Schmidt wrote:
On Aug 11, 2014, at 12:39 PM, Sean Farley wrote:
Anyone who had the previous file, including our automated systems, will
now encounter a checksum mismatch. To fix this please follow the
On Aug 12, 2014, at 9:26 AM, Daniel J. Luke wrote:
it wouldn't be horrible if setting a revision just changed dist_subdir
automatically (even when it's not necessary), which I think is what Sean was
suggesting.
In addition, a stealth update does not imply that the revision needs to be
On Aug 12, 2014, at 11:04 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 12, 2014, at 9:26 AM, Daniel J. Luke wrote:
it wouldn't be horrible if setting a revision just changed dist_subdir
automatically (even when it's not necessary), which I think is what Sean was
suggesting.
In
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec mo...@macports.org wrote:
Now about 5.8-5.16: my idea was to initially set the INC path for
those versions in such a way that it would include
5.16.3/darwin-thread-multi-2level 5.16.3
5.16.1/darwin-thread-multi-2level 5.16.1
On Aug 12, 2014, at 11:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
But I'm unable to figure out how to patch Perl to do that. The INC
path additions seem to be ignored.
Why handle = 5.16 differently than = 5.18?
why handle any of them?
maybe just spend the time fixing any ports
On Aug 12, 2014, at 10:06 AM, Daniel J. Luke wrote:
On Aug 12, 2014, at 11:04 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:26 AM, Daniel J. Luke wrote:
it wouldn't be horrible if setting a revision just changed dist_subdir
automatically (even when it's not necessary), which I think is
On Aug 12, 2014, at 10:08 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 12, 2014, at 11:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
But I'm unable to figure out how to patch Perl to do that. The INC
path additions seem to be ignored.
Why handle = 5.16 differently than =
On Aug 12, 2014, at 11:11 AM, Ryan Schmidt ryandes...@macports.org wrote:
It's still not totally automatic: the developer still has to update the
checksums, so if the developer is sufficiently aware that the checksums need
to be updated, why can't the developer also follow the stealth
On Aug 12, 2014, at 11:12 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 12, 2014, at 10:08 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 12, 2014, at 11:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
But I'm unable to figure out how to patch Perl to do that. The INC
On Aug 12, 2014, at 10:15 AM, Daniel J. Luke dl...@geeklair.net wrote:
I'm just saying, it's a /lot/ of effort to do this for p5.8-p5.20 ports when
it could be reduced (somewhat) by just working on p5.20... (and
deprecating/removing everything else).
It seems to me an order of magnitude
On 8/12/14 7:56 AM, Mojca Miklavec wrote:
On Tue, Aug 12, 2014 at 4:43 PM, David Evans wrote:
I'd be happy to help with this. It's true that many ports are outdated
version-wise (even ones that have already been ported to p5.20)
and my recent experience suggests that many need updated
On Tue, Aug 12, 2014 at 11:15 AM, Daniel J. Luke dl...@geeklair.net wrote:
I'm just saying, it's a /lot/ of effort to do this for p5.8-p5.20 ports
when it could be reduced (somewhat) by just working on p5.20... (and
deprecating/removing everything else).
Also worth noting: the current Perl
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec mo...@macports.org wrote:
Now about 5.8-5.16: my idea was to initially set the INC path for
those versions in such a way that it would include
5.16.3/darwin-thread-multi-2level 5.16.3
On Aug 12, 2014, at 11:19 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 12, 2014, at 10:15 AM, Daniel J. Luke dl...@geeklair.net wrote:
I'm just saying, it's a /lot/ of effort to do this for p5.8-p5.20 ports when
it could be reduced (somewhat) by just working on p5.20... (and
On Aug 12, 2014, at 10:20 AM, David Evans dev...@macports.org wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec mo...@macports.org wrote:
Now about 5.8-5.16: my idea was to initially set the INC path for
those versions in such a way that it would
On Aug 12, 2014, at 10:22 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 12, 2014, at 11:19 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 12, 2014, at 10:15 AM, Daniel J. Luke dl...@geeklair.net wrote:
I'm just saying, it's a /lot/ of effort to do this for p5.8-p5.20
On Aug 12, 2014, at 11:25 AM, Ryan Schmidt ryandes...@macports.org wrote:
that's pretty much why we're in the situation we are now - we just continue
with the current setup because it's 'easier'. Someone puts a bunch of effort
into making things work with a newer (but never the current)
On Aug 12, 2014, at 10:28 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 12, 2014, at 11:25 AM, Ryan Schmidt ryandes...@macports.org wrote:
that's pretty much why we're in the situation we are now - we just continue
with the current setup because it's 'easier'. Someone puts a bunch
On 8/12/14 8:23 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 10:20 AM, David Evans dev...@macports.org wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec mo...@macports.org wrote:
Now about 5.8-5.16: my idea was to initially set the INC path for
those
On Tue, Aug 12, 2014 at 5:23 PM, Ryan Schmidt wrote:
On Aug 12, 2014, at 10:20 AM, David Evans wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec wrote:
Now about 5.8-5.16: my idea was to initially set the INC path for
those versions in such a way that
On Aug 12, 2014, at 10:03 AM, Mojca Miklavec mo...@macports.org wrote:
On Tue, Aug 12, 2014 at 5:23 PM, Ryan Schmidt wrote:
On Aug 12, 2014, at 10:20 AM, David Evans wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec wrote:
Now about 5.8-5.16: my idea
At 8:32 AM -0700 8/12/14, David Evans wrote:
On 8/12/14 8:23 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 10:20 AM, David Evans dev...@macports.org wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca Miklavec mo...@macports.org wrote:
Now about 5.8-5.16: my
Is there data coming in through mpstats that could help with this
decision? What is the distribution of perl installs by version?
No helpful data from mpstats at the moment. Don't bother checking.
--
Clemens Lang
___
macports-dev mailing list
On Aug 12, 2014, at 8:45 AM, Mojca Miklavec mo...@macports.org wrote:
On Tue, Aug 12, 2014 at 4:30 PM, Daniel J. Luke wrote:
On Aug 12, 2014, at 10:15 AM, Mojca Miklavec wrote:
Other than that I can definitely create a new branch to simplify
testing and add the same patch to all perl
On 8/12/14 9:30 AM, Frank Schima wrote:
On Aug 12, 2014, at 10:03 AM, Mojca Miklavec mo...@macports.org wrote:
On Tue, Aug 12, 2014 at 5:23 PM, Ryan Schmidt wrote:
On Aug 12, 2014, at 10:20 AM, David Evans wrote:
On 8/12/14 8:06 AM, Ryan Schmidt wrote:
On Aug 12, 2014, at 9:56 AM, Mojca
On Aug 12, 2014, at 10:30 AM, Frank Schima m...@macports.org wrote:
For me, the only thing holding up moving to perl 5.20 is p5.20-pdo, 5.20-wx
and possibly a few others that work fine with p5.16.
I meant p5-pdl here.
-Frank
___
macports-dev
On Tue, Aug 12, 2014 at 6:43 PM, David Evans wrote:
On 8/12/14 9:30 AM, Frank Schima wrote:
I see no reason to change perl 5.16 or lower because they are already
working. Let’s just look forward to 5.18 and 5.20. Even if 5.18 is a lame
duck already.
For me, the only thing holding up
Another thing that I noticed: running installer in trace mode reveals
many missing basic dependencies in basically all modules.
Typical example:
Warning: An activity was attempted outside sandbox:
/opt/local/lib/perl5/vendor_perl/5.18/ExtUtils/Liblist.pm
Warning: An activity was attempted
On Jul 6, 2014, at 8:28 PM, Perry E. Metzger pe...@piermont.com wrote:
Howdy;
I've been waiting for the maintainer to respond to the ticket I
filed eight months ago about the macports libetpan being very, very
obsolete. Original is here:
https://trac.macports.org/ticket/41037
On Tue, Aug 12, 2014 at 08:19:27AM -0700, David Evans wrote:
As Daniel has said, no point in changing things that are going to go away so
we need to get a consensus on where we want to go with this. My input here
would be this:
* make the necessary changes to perl5.18 to work as perl5.20
On Aug 12, 2014, at 5:25 PM, Dan Ports dpo...@macports.org wrote:
On Tue, Aug 12, 2014 at 08:19:27AM -0700, David Evans wrote:
As Daniel has said, no point in changing things that are going to go away so
we need to get a consensus on where we want to go with this. My input here
would be
On Tue, 12 Aug 2014 15:14:11 -0600 Frank Schima m...@macports.org
wrote:
On Jul 6, 2014, at 8:28 PM, Perry E. Metzger pe...@piermont.com
wrote:
Howdy;
I've been waiting for the maintainer to respond to the ticket I
filed eight months ago about the macports libetpan being very,
On 2014-8-13 07:14 , Frank Schima wrote:
On Jul 6, 2014, at 8:28 PM, Perry E. Metzger pe...@piermont.com wrote:
Howdy;
I've been waiting for the maintainer to respond to the ticket I
filed eight months ago about the macports libetpan being very, very
obsolete. Original is here:
49 matches
Mail list logo
