> On 2018-03-06, at 16:07, Ken Cunningham
> wrote:
>
>
> On 2018-03-06, at 7:01 AM, macpo...@parvis.nl wrote:
>
>> I'm trying to local install jdupes with my own test fixes, but i cannot
>> destroot/activate due to more violation.
>
>> Warning: violation by /usr
>
>
>> fragment of origina
On Mon, 5 Mar 2018, Ryan Schmidt wrote:
Don't tell me that Perl 5.26 comes with a built-in time-bomb...
Add -I to CPPFLAGS. Perl < 5.26 did so automatically, but 5.26 no longer
does.
Well, "-I." actually; thanks.
Hmmm... I wonder how that slipped past me? It must've got nobbled on my
re
On 6 Mar 2018, at 15:50, Ken Cunningham wrote:
> port peg PORTNAME
brew pin FORMULA? There shouldn't be shame in mentioning it. As Arno pointed
out, it gets tricky with deps, it's eventually overridden if necessary.
As I raised in another topic, port upgrade could preempt building ports with
o
In Dave's case, he's running a perl script and not building with a compiler -
so it's not CPPFLAGS but rather @INC changes with perl 5.26 that he's seeing.
As always, changes are described in perldelta:
http://search.cpan.org/dist/perl-5.26.0/pod/perldelta.pod#Removal_of_the_current_directory_("
Oh man, if this exists and I didn't know about it, wouldn't that be something.
If that's the case, many don't know about it, based on the innumerable tickets
and issues that are raised by this.
How do you use --no-upgrade, exactly?
Ken
On 2018-03-06, at 7:10 AM, G Alexander wrote:
>
> isnt
On 2018-03-06, at 7:01 AM, macpo...@parvis.nl wrote:
> I'm trying to local install jdupes with my own test fixes, but i cannot
> destroot/activate due to more violation.
> Warning: violation by /usr
> fragment of original Makefile:
> --
> # PREFIX determines where
I'm trying to local install jdupes with my own test fixes, but i cannot
destroot/activate due to more violation.
how can i - without patching the Makefile, specify /opt/local as destination?
logextract:
---
# port install jdupes
---> Fetching distfiles for jdupes
---> Attempting to fet
On Mar 6, 2018, at 04:00, db wrote:
> On 6 Mar 2018, at 10:49, Ryan Schmidt wrote:
>> The portindex indexes Portfiles, not portgroups. So the port's version must
>> be set in the Portfile, not anywhere else.
>
> Would then portindex fail if the port's version in the portfile is a variable
> set
On 6 Mar 2018, at 10:49, Ryan Schmidt wrote:
> The portindex indexes Portfiles, not portgroups. So the port's version must
> be set in the Portfile, not anywhere else.
Would then portindex fail if the port's version in the portfile is a variable
set to a command?
On Mar 6, 2018, at 03:47, db wrote:
> On 6 Mar 2018, at 02:34, Ryan Schmidt wrote:
>> On Mar 5, 2018, at 05:43, db wrote:
>>> As I said in my previous post, you can get HEAD's hash with 'git ls-remote
>>> --heads'. And store it somewhere.
>> Who are you suggesting should run this command and when?
On 6 Mar 2018, at 02:34, Ryan Schmidt wrote:
> On Mar 5, 2018, at 05:43, db wrote:
>> As I said in my previous post, you can get HEAD's hash with 'git ls-remote
>> --heads'. And store it somewhere.
> Who are you suggesting should run this command and when? The port maintainer?
> The user trying
On Mar 5, 2018, at 22:09, Ryan Schmidt wrote:
> On Mar 5, 2018, at 20:06, Dave Horsfall wrote:
>
>> A script that I wrote and has worked fine for ages is now breaking with:
>>
>> Can't locate Scanner.pm in @INC (you may need to install the Scanner
>> module) (@INC contains:
>> /opt/local/li
12 matches
Mail list logo
