Re: MacPorts Developer Meeting?

On Wed, Jul 23, 2014 at 6:06 AM, Lawrence Velázquez wrote: > On Apr 4, 2014, at 3:22 PM, Mojca Miklavec wrote: > >> If you are interested in coming, maybe you can also add the continent >> of your choice to the reply ;) > > Can't say for sure what I'll be up to in 2015, but I'd be interested. I'm

Re: Maintainers census

On Jul 22, 2014, at 2:11 PM, Arno Hautala wrote: > "BCC" because you know someone is going to start a "Reply All; Please > take me off this mailing list" fire. Plus, you're conducting a census, > not a discussion. +1 vq ___ macports-dev mailing list m

Re: MacPorts Developer Meeting?

On Apr 4, 2014, at 3:22 PM, Mojca Miklavec wrote: > If you are interested in coming, maybe you can also add the continent > of your choice to the reply ;) Can't say for sure what I'll be up to in 2015, but I'd be interested. I'm currently in New York. vq (Sorry to dredge this up after so many

Re: What would YOU like to see 'port doctor' do?

On Jul 21, 2014, at 4:33 PM, Kyle Sammons wrote: > I've been working on a command, "port doctor" that checks for common issues > in the user's environment. I've implemented just about everything I, Michael > D, Snc, and Neverpanic can think of, so I was wondering if you guys had > anything els

Re: perl5.20

On Jul 22, 2014, at 12:37 PM, Daniel J. Luke wrote: > (and/or won't rev-upgrade just fix these when upgrading perl? if it doesn't, > can we just make it fix them?) rev-upgrade is a way for people to discover ports that are linked improperly that need to be fixed. rev-upgrade itself is not the

Re: [120162] trunk/dports/lang/qore-mysql-module

On Jul 22, 2014, at 11:56 AM, Petr Vaněk wrote: > is there any way how to tell "we don't care about mysql client > version, just use a 'default one'"? > > Something like RPM: BuildRequires: mysql-client? No; a port must pick a specific one, or ideally offer variants. _

Re: What would YOU like to see 'port doctor' do?

On Tue, Jul 22, 2014 at 8:23 PM, Mihai Moldovan wrote: > Will `doctor` error if something like this is being found? Some software > likes > to install headers and dylibs to those locations and MacPorts should in > theory > not be affected when using -(i)sysroot. > "In theory." Practice has shown

Re: [122412] trunk/dports

On Jul 22, 2014, at 10:46 AM, David Evans wrote: > Looks like openvas-libraries needs to be rebuilt as well. True! I had given up on openvas after failing to update it to the latest version [1] but the old version does still build so I revbumped it [2]. [1] https://trac.macports.org/ticket/25

Re: What would YOU like to see 'port doctor' do?

Quick and probably stupid question here. * On 21.07.2014 11:33 pm, Kyle Sammons wrote: > - Dylibs in /usr/local/lib > - Header files in /usr/local/include Will `doctor` error if something like this is being found? Some software likes to install headers and dylibs to those locations and MacPorts

Re: perl5.20

On Tue, Jul 22, 2014 at 11:35 PM, Frank Schima wrote: > > I have a bunch of p5 port changes ready to commit, but I wanted to test the > p5.20 versions first to see if they at least build. Can you please test the following patch? https://trac.macports.org/ticket/43480#comment:4 Mojca _

Re: perl5.20

On Tue, Jul 22, 2014 at 7:37 PM, Daniel J. Luke wrote: > On Jul 22, 2014, at 11:51 AM, Mojca Miklavec wrote: >> >> On Jul 19, 2014 1:15 AM, "David Evans" wrote: >> > On 7/18/14 3:47 PM, Mojca Miklavec wrote: >> > Well, I'm sorry but I don't really see the need for these experiments. >> >> At the mo

Re: perl5.20

On Jul 22, 2014, at 3:35 PM, Frank Schima wrote: > We still have a number of ports that require perl 5.12 right now however. So > we may not be able to remove that yet. I will try to file a ticket about this > soon if one has not been created (I forget at this point). I have just now created

Re: perl5.20

On 7/22/14 2:35 PM, Frank Schima wrote: > BTW, Mojca is a “she”. :) Oops, boy is my face red. Please accept my apologies, Mojca! Dave ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-

Re: perl5.20

On Jul 22, 2014, at 3:25 PM, David Evans wrote: > On 7/22/14 1:01 PM, Daniel J. Luke wrote: >>> I think it is way too early to be switching to it by default. Much less the >>> only option. So I vote we at least keep perl 5.16 and perl 5.18 and all of >>> their modules around for a while. >>

Re: perl5.20

On Jul 22, 2014, at 5:25 PM, David Evans wrote: > > On 7/22/14 1:01 PM, Daniel J. Luke wrote: >>> I think it is way too early to be switching to it by default. Much less the >>> only option. So I vote we at least keep perl 5.16 and perl 5.18 and all of >>> their modules around for a while. >>

Re: perl5.20

On 7/22/14 1:01 PM, Daniel J. Luke wrote: >> I think it is way too early to be switching to it by default. Much less the >> only option. So I vote we at least keep perl 5.16 and perl 5.18 and all of >> their modules around for a while. > only perl5.18 currently has a maintainer in MacPorts. > >

Re: perl5.20

On Jul 22, 2014, at 3:50 PM, Frank Schima wrote: > > On Jul 22, 2014, at 11:37 AM, Daniel J. Luke wrote: >> So here's my short proposal: >> >> 1. switch the perl5 port to actually install perl5.20.x >> 2. deprecate and remove the other perl5.x ports >> 3. change the perl5 portgroup to just buil

Re: perl5.20

On Jul 22, 2014, at 11:37 AM, Daniel J. Luke wrote: > So here's my short proposal: > > 1. switch the perl5 port to actually install perl5.20.x > 2. deprecate and remove the other perl5.x ports > 3. change the perl5 portgroup to just build/install p5 ports that work with > whatever we install as

Re: What would YOU like to see 'port doctor' do?

On Tue, Jul 22, 2014 at 2:01 PM, Kyle Sammons wrote: > There are some more unusual ways that people manage to break their >> systems, like replacing executables (sed, tar, etc...) in /usr/bin with >> incompatible versions (or just deleting them). I'm not sure if you want >> to go down that rabbit

Re: Maintainers census

On Tue, Jul 22, 2014 at 1:33 PM, Frank Schima wrote: > > Any thoughts or suggestions? It might be usefull to include the list of ports that the maintainer is listed on. Or at least implore the receiver to check on their end. Bonus points for including the commands they need to run. Of course, thi

Re: What would YOU like to see 'port doctor' do?

Hey Joshua, On 7/21/14, 11:47 PM, Joshua Root wrote If you're going to check these, you might as well check for sqlite and openssl too. We also need the system's tclsh for building from source, which includes selfupdate. Done. I assume you're using the $prefix variable here, not hardcoding /op

Re: perl5.20

On Jul 22, 2014, at 11:51 AM, Mojca Miklavec wrote: > > On Jul 19, 2014 1:15 AM, "David Evans" wrote: > > On 7/18/14 3:47 PM, Mojca Miklavec wrote: > > Well, I'm sorry but I don't really see the need for these experiments. > > At the moment it is very inconvenient to upgrade perl from 5.x.y to

Maintainers census

Hi all, I was thinking of running a quick census of maintainers to help cull inactive port maintainers. My idea is to create a list of all maintainers. I started by listing all port maintainers (port info --maintainers all) to a text file and massaging it with some easy search and replaces to

Re: What would YOU like to see 'port doctor' do?

On Tue, Jul 22, 2014 at 2:28 AM, Joshua Root wrote: > On 2014-7-22 10:08 , Adam Dershowitz wrote: >> >> Checking for files that should not be in macports directory, that end up >> being there. They could be left either by an old install, or by a different >> installer that inappropriately put t

Re: perl5.20

On Jul 19, 2014 1:15 AM, "David Evans" wrote: > On 7/18/14 3:47 PM, Mojca Miklavec wrote: > > Well, I'm sorry but I don't really see the need for these experiments. At the moment it is very inconvenient to upgrade perl from 5.x.y to 5.x.(y+1). A bunch of "random" ports become broken "just because"

Re: [122412] trunk/dports

On 7/22/14 5:41 AM, ryandes...@macports.org wrote: > [122412] trunk/dports > > Revision > 122412 > Author > ryandes...@macports.org > Date > 2014-07-22 05:41:54 -0700 (Tue, 22 Jul 2014) > > > Log Message > > libgcrypt: update to 1.6.1 a

Re: What would YOU like to see 'port doctor' do?

On Tue, Jul 22, 2014 at 2:47 AM, Joshua Root wrote: > There are some more unusual ways that people manage to break their > systems, like replacing executables (sed, tar, etc...) in /usr/bin with > incompatible versions (or just deleting them). I'm not sure if you want > to go down that rabbit hol

Re: What would YOU like to see 'port doctor' do?

Hello, A few ideas if they haven't been mentioned: - Check all local sources (sources.conf) - If there are Portfiles in sub-folder, if PortIndex exists - If the system port has a newer version - Any duplicate ports in multiple local sources - Multiple $PATH entries in shell startup f

Re: [122361] trunk/dports/games/pioneers

On Jul 21, 2014, at 11:01 AM, s...@macports.org wrote: > Revision > 122361 > Author > s...@macports.org > Date > 2014-07-21 09:01:19 -0700 (Mon, 21 Jul 2014) > Log Message > > pioneers: update to 15.2 > Modified Paths > > • trunk/dports/games/pioneers/Portfile > +depends_lib port