On Tue, Nov 12, 2013 at 10:52:20PM +0100, Peter Danecek wrote:
> I tried to run in trace mode, however, I have not installed base from
> trunk, so I am not sure if it is already reporting correctly.
If it doesn't outright crash or fail to build, it might be better than
nothing, but trace mode in 2
Hi all,
I tried to respect the recommendations here and this is what I came up with:
http://trac.macports.org/ticket/41337
I tried to run in trace mode, however, I have not installed base from trunk, so
I am not sure if it is already reporting correctly. It would report to a
missing libgcc de
On 2013-11-10 23:23 , Michael Dickens wrote:
> On Sun, Nov 10, 2013, at 12:47 AM, Joshua Root wrote:
>> On 2013-11-10 05:35 , Craig Treleaven wrote:
>>> Perhaps just the
>>> documentation for depends_lib should be expanded to say that it
>>> indicates both compiled and interpreted linkages?
>>
>> I
On Nov 10, 2013, at 7:23 AM, Michael Dickens wrote:
> How does one indicate a runtime dependency that is checked for at
> configure time and not used for building or linking?
As previously stated, one could use either depends_lib or depends_build +
depends_run, because depends_lib does not curr
Depends_build and depends_lib are installed prior to build phase, and
depends_run prior to activate. Depends_extract for extract phase, etc.
So a dependency marked as depends_run will not be installed prior to
configuration.
On Sun, 10 Nov 2013 07:23:47 -0500, Michael Dickens
wrote:
O
On Sun, Nov 10, 2013, at 12:47 AM, Joshua Root wrote:
> On 2013-11-10 05:35 , Craig Treleaven wrote:
> > Perhaps just the
> > documentation for depends_lib should be expanded to say that it
> > indicates both compiled and interpreted linkages?
>
> It doesn't indicate anything about linkage, it ind
On 2013-11-10 05:35 , Craig Treleaven wrote:
> Perhaps just the
> documentation for depends_lib should be expanded to say that it
> indicates both compiled and interpreted linkages?
It doesn't indicate anything about linkage, it indicates that the
dependency is needed at both build time and run ti
On Nov 9, 2013, at 12:35, Craig Treleaven wrote:
> My port uses p5.12-libwww-perl which relies on a list of other perl modules.
You should actually declare dependencies on the specific other modules that you
use, not libwww-perl itself anymore.
$ port notes p5-libwww-perl
p5-libwww-perl has t
Speaking of my script, I've made a bunch of changes to it recently, so I'll
probably need to create a new tag sometime so I can update the
`macportsscripts` port that points to it... The version from 0.1.4 still
reports library links that are there due to libtool overlinking, and I've
been working
On Nov 9, 2013, at 1:35 PM, Craig Treleaven wrote:
> So, in a way, we all use depends_lib for certain things as a short-hand for
> listing stuff as both depends_build and depends_run, no?
That's the general usage, yes.
> In a perfect world, maybe we should have a "depends_mod" for indicating a
At 11:48 AM -0500 11/9/13, Jeremy Lavergne wrote:
Myth includes Perl and Python bindings that need a number of
dependencies to work (eg port:${pymodver}-mysql,
port:${perlmodver}-dbd-mysql, etc). I have these listed as
depends_lib but no Myth binaries link directly to them. Is it
advantageou
Myth includes Perl and Python bindings that need a number of
dependencies to work (eg port:${pymodver}-mysql,
port:${perlmodver}-dbd-mysql, etc). I have these listed as depends_lib
but no Myth binaries link directly to them. Is it advantageous to list
them instead as depends_run?
The pa
At 4:27 PM +0100 11/1/13, Clemens Lang wrote:
On Fri, Nov 01, 2013 at 10:27:04AM +1100, Joshua Root wrote:
If they are needed at build time and runtime, use depends_lib. If they
are only needed at runtime, use depends_run.
is there any difference between listing a package in both depends_bui
On 2013-11-2 10:12 , Ryan Schmidt wrote:
> On Nov 1, 2013, at 17:25, Joshua Root wrote:
>
>> On 2013-11-2 02:27 , Clemens Lang wrote:
>>
>>> I'm currently trying to improve trace mode to a point where every
>>> package I have installed builds fine using trace mode and I've come
>>> across the gcc
On Nov 1, 2013, at 17:25, Joshua Root wrote:
> On 2013-11-2 02:27 , Clemens Lang wrote:
>
>> I'm currently trying to improve trace mode to a point where every
>> package I have installed builds fine using trace mode and I've come
>> across the gcc ports, which set
>> depends_run port:ld64 port:c
On 2013-11-2 02:27 , Clemens Lang wrote:
> Hi,
>
> On Fri, Nov 01, 2013 at 10:27:04AM +1100, Joshua Root wrote:
>> If they are needed at build time and runtime, use depends_lib. If they
>> are only needed at runtime, use depends_run.
>
> is there any difference between listing a package in both d
On Nov 1, 2013, at 4:15 PM, Ryan Schmidt wrote:
> On Nov 1, 2013, at 15:09, Daniel J. Luke wrote:
>> which again, you're assuming that no port has a runtime dependency on a
>> library that doesn't link with that library (which a reasonable person might
>> express as a depends_run dependency). T
On Nov 1, 2013, at 15:09, Daniel J. Luke wrote:
> which again, you're assuming that no port has a runtime dependency on a
> library that doesn't link with that library (which a reasonable person might
> express as a depends_run dependency). This is #2 from above.
>
> The only way you can assu
On Nov 1, 2013, at 4:04 PM, Ryan Schmidt wrote:
> On Nov 1, 2013, at 15:02, Daniel J. Luke wrote:
>> On Nov 1, 2013, at 3:58 PM, Ryan Schmidt wrote:
>>> On Nov 1, 2013, at 14:55, Daniel J. Luke wrote:
On Nov 1, 2013, at 3:50 PM, Ryan Schmidt wrote:
> On Nov 1, 2013, at 14:44, Daniel J
On Nov 1, 2013, at 15:02, Daniel J. Luke wrote:
> On Nov 1, 2013, at 3:58 PM, Ryan Schmidt wrote:
>> On Nov 1, 2013, at 14:55, Daniel J. Luke wrote:
>>> On Nov 1, 2013, at 3:50 PM, Ryan Schmidt wrote:
On Nov 1, 2013, at 14:44, Daniel J. Luke wrote:
> On Nov 1, 2013, at 2:09 PM, Ryan
On Nov 1, 2013, at 3:58 PM, Ryan Schmidt wrote:
> On Nov 1, 2013, at 14:55, Daniel J. Luke wrote:
>> On Nov 1, 2013, at 3:50 PM, Ryan Schmidt wrote:
>>> On Nov 1, 2013, at 14:44, Daniel J. Luke wrote:
On Nov 1, 2013, at 2:09 PM, Ryan Schmidt wrote:
> The solution would be for ports that
On Nov 1, 2013, at 14:55, Daniel J. Luke wrote:
> On Nov 1, 2013, at 3:50 PM, Ryan Schmidt wrote:
>> On Nov 1, 2013, at 14:44, Daniel J. Luke wrote:
>>> On Nov 1, 2013, at 2:09 PM, Ryan Schmidt wrote:
The solution would be for ports that use the ImageMagick libraries to
depend on it v
On Nov 1, 2013, at 3:50 PM, Ryan Schmidt wrote:
> On Nov 1, 2013, at 14:44, Daniel J. Luke wrote:
>> On Nov 1, 2013, at 2:09 PM, Ryan Schmidt wrote:
>>> The solution would be for ports that use the ImageMagick libraries to
>>> depend on it via depends_lib and for those only needing its programs t
On Nov 1, 2013, at 14:44, Daniel J. Luke wrote:
> On Nov 1, 2013, at 2:09 PM, Ryan Schmidt wrote:
>> I’m not sure if there’s any licensing difference. Historically, we’ve said
>> that if a dependency is needed at build time and at runtime, then it should
>> be listed in only depends_lib, even if
On Nov 1, 2013, at 2:09 PM, Ryan Schmidt wrote:
> I’m not sure if there’s any licensing difference. Historically, we’ve said
> that if a dependency is needed at build time and at runtime, then it should
> be listed in only depends_lib, even if it is not a library. However I think
> we should ch
We use “installs_libs no” to indicate that a port that other ports depend on
does not install any libraries.
That’s no help when the port does install libraries, like ImageMagick does.
On Nov 1, 2013, at 13:11, Jeremy Lavergne wrote:
> I think we use `installs_libs no` for those licensing che
I think we use `installs_libs no` for those licensing checks.
On Nov 1, 2013, at 14:09, Ryan Schmidt wrote:
> I’m not sure if there’s any licensing difference. Historically, we’ve said
> that if a dependency is needed at build time and at runtime, then it should
> be listed in only depends_lib
On Nov 1, 2013, at 10:27, Clemens Lang wrote:
> is there any difference between listing a package in both depends_build
> and depends_run compared to just listing it in depends_lib, e.g. in how
> licensing stuff propagates?
I’m not sure if there’s any licensing difference. Historically, we’ve sa
On Fri, Nov 01, 2013 at 04:27:40PM +0100, Clemens Lang wrote:
> I'm currently trying to improve trace mode to a point where every
> package I have installed builds fine using trace mode and I've come
> across the gcc ports, which set
> depends_run port:ld64 port:cctools
> but fail to configure wh
Hi,
On Fri, Nov 01, 2013 at 10:27:04AM +1100, Joshua Root wrote:
> If they are needed at build time and runtime, use depends_lib. If they
> are only needed at runtime, use depends_run.
is there any difference between listing a package in both depends_build
and depends_run compared to just listing
On 2013-11-1 05:54 , Peter Danecek wrote:
>
> Hi all,
>
> I'm somewhat puzzled with the dependencies of some ports, and I realise the I
> lack some basic understanding.
>
> (1) py-cython
>
> From what I understand, build dependencies are required during the build, but
> can be removed later.
On Oct 31, 2013, at 2:54 PM, Peter Danecek wrote:
> (2) python package dependencies
>
> Intuitively, I would say that most python package dependencies were lib
> dependencies. But they actually may install without, right? So is it okay to
> declare them lib dependencies or might it be better t
Peter,
You would add those to the build dependencies with depends_build-append. I
haven't installed myself, but I'm guessing they aren't too large, so if that's
the case, I wouldn't have an issue with that.
Blair
On 10/31/13 12:17 PM, Peter Danecek wrote:
Blair,
Thanks for the quick reply
Blair,
Thanks for the quick reply. I would have another one: It is a python package. I
have some dependencies, which actually are not needed for package itself but
only for testing. Testing is non done by the port itself. So I would have not
included these dependencies, i.e. `py-nose`, `py-pep
On 10/31/13 11:54 AM, Peter Danecek wrote:
Hi all,
I'm somewhat puzzled with the dependencies of some ports, and I realise the I
lack some basic understanding.
(1) py-cython
From what I understand, build dependencies are required during the build, but
can be removed later. Also they are no
Hi all,
I'm somewhat puzzled with the dependencies of some ports, and I realise the I
lack some basic understanding.
(1) py-cython
From what I understand, build dependencies are required during the build, but
can be removed later. Also they are not required for installation of prebuilt
packa
36 matches
Mail list logo
