Re: GSoC Project: Revitalizing Pallet

Hi Kyle, On 07/05/2015, at 8:14 AM, Kyle Sammons wrote: > My name's Kyle Sammons and I've been accepted into this years GSoC. I was > also a GSoC participant for MacPorts last year working on Project "Clean-up > Stuff", which created the "port doctor" and "port reclaim" commands. I had been hop

Re: [136885] trunk/dports/devel/cableswig/Portfile

Well that's embarrassing. Now we're even, after the libjpeg-turbo / muniversal business :P :P vq > On May 29, 2015, at 1:18 AM, ryandes...@macports.org wrote: > > Revision > 136885 Author > ryandes...@macports.org Date

Re: how to: meta-package port

On Thursday May 28 2015 12:27:19 Lawrence Velázquez wrote: > Install some dummy files instead of failing. Something like this: > > PortSystem 1.0 > name foo > supported_archs noarch > archive_sites > distfiles > use_configure no > build {} > destroot { > sy

Re: how to: meta-package port

On May 28, 2015, at 11:48 AM, René J.V. Bertin wrote: > What was the magic formula again to use in a meta-package port that only > exists to pull in (depend on) a number of other ports? Just supported_archs > noarch together with an error message in the pre-fetch? Install some dummy files inst

how to: meta-package port

Hi, What was the magic formula again to use in a meta-package port that only exists to pull in (depend on) a number of other ports? Just supported_archs noarch together with an error message in the pre-fetch? Thanks, R. ___ macports-dev mailing list m

Re: port:bzip2 missing dependency

On Thursday May 28 2015 17:09:08 Rainer Müller wrote: >On 2015-05-28 16:49, René J.V. Bertin wrote: >bzip2 does not even have a configure script. The build rules in its >Makefile are also really simple and do not look for any external >binaries (except compiler and linker, of course). You must be

Re: port:bzip2 missing dependency

On 2015-05-28 16:49, René J.V. Bertin wrote: > I was playing around with MacPorts on Linux, and there the bzip2 > configure script failed because if couldn't find m4. Once I installed > port:m4 first (and removed the obsolete 1st hunk from the > linux-specific patch), port:bzip2 built. bzip2 does

Re: port:bzip2 missing dependency

On Thursday May 28 2015 16:19:30 Rainer Müller wrote: >How did you come to this conclusion? I was playing around with MacPorts on Linux, and there the bzip2 configure script failed because if couldn't find m4. Once I installed port:m4 first (and removed the obsolete 1st hunk from the linux-spec

Re: Programmatically finding dependencies for a Portfile

On 2015-05-28 15:42, Artur Szostak wrote: > How should this work without configuring sources.conf? > I dont think I understand what you mean by port directory. While the problem at hand was already solved with the other answer, I still typed this as it might be useful for someone else stumbling ac

Re: port:bzip2 missing dependency

On 2015-05-28 15:39, René J.V. Bertin wrote: > A quick bug report outside of trac: port:bzip2 is missing a > dependency on m4, which probably should have been noticed before by > users installing to a non-default prefix that requires building from > scratch? How did you come to this conclusion? W

RE: Programmatically finding dependencies for a Portfile

Thanks, set mport [mportopen "file:///tmp/testport" [list subport "testsubport"] [list]] Is exactly what is needed to select data for a specific subport. Cheers Artur From: Rainer Müller [rai...@macports.org] Sent: 28 May 2015 15:45 To: Artur Szost

Re: Programmatically finding dependencies for a Portfile

On 2015-5-28 22:44 , Artur Szostak wrote: > Hi, > > Given a Portfile, I am trying to programmatically find all of its direct > dependencies. My approach is to execute an appropriate TcL script in > port-tclsh to produce a listing of such dependencies. I am able to handle > Portfiles with the ex

Re: Programmatically finding dependencies for a Portfile

On 2015-05-28 14:44, Artur Szostak wrote: > package require macports > mportinit > set mport [mportopen "file:///tmp/testport" [list] [list]] If you want a specific subport, you would need to give its name in the list of options here. This list of options consists of pairs of key and value as list

RE: Programmatically finding dependencies for a Portfile

How should this work without configuring sources.conf? I dont think I understand what you mean by port directory. Alternatively, where is the meat of 'port rdeps' implemented? I could try extract the code I need from there. From: René J.V. Bertin [rjvber.

port:bzip2 missing dependency

Hi, A quick bug report outside of trac: port:bzip2 is missing a dependency on m4, which probably should have been noticed before by users installing to a non-default prefix that requires building from scratch? R. ___ macports-dev mailing list macports

Re: Programmatically finding dependencies for a Portfile

On Thursday May 28 2015 12:44:57 Artur Szostak wrote: >Given a Portfile, I am trying to programmatically find all of its direct >dependencies. `port rdeps ` or simply `port rdeps` inside a port directory that is not installed or shadowed by another port tree? R. __

Programmatically finding dependencies for a Portfile

Hi, Given a Portfile, I am trying to programmatically find all of its direct dependencies. My approach is to execute an appropriate TcL script in port-tclsh to produce a listing of such dependencies. I am able to handle Portfiles with the example script indicated below, but only for Portfiles t

Re: [136236] trunk/dports/science/mpich/Portfile

> On May 12, 2015, at 3:32 PM, ebori...@macports.org wrote: > > Revision > 136236 > Author > ebori...@macports.org > Date > 2015-05-12 13:32:05 -0700 (Tue, 12 May 2015) > Log Message > > mpich-*: Initial attempt at gcc5/6 support. See #47541. > Modified Paths > • trunk/dports/science/mpic