Re: Questions on dependencies
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_build
and depends_run compared to just listing it in depends_lib, e.g. in how
licensing stuff propagates?
Since MacPorts ensures depends_run dependencies are installed before
attempting to build a package, we usually do not notice a depends_run
dependency that should rather be depends_build.
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 when trace mode (correctly) hides files installed
by these ports. I wonder whether the correct fix would be to convert
those into depends_lib, or just add them as depends_build, too.
I was playing with egall's port-depcheck.sh script:
https://github.com/cooljeanius/macportsscripts/blob/v0.1.4/port-depcheck.sh
It identified several interesting things in my MythTV ports that I
hadn't known before--including a couple more opportunistic links
(Myth is so promiscuous!).
A couple of questions for the more-experienced here.
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?
egall's script says that Myth does not link directly to
qt4-mac-${mysqlver}-plugin but does link directly to qt4-mac. Again,
are there advantages to showing qt4-mac as a depends_lib but the
plugin as a depends_run?
I'm not a professional developer; just trying to understand a little more.
Thanks,
Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [113088] trunk/dports/net/openssh/Portfile
Hi, On Fri, Nov 08, 2013 at 06:54:28AM -0800, ciserl...@macports.org wrote: > Revision: 113088 > https://trac.macports.org/changeset/113088 > Author: ciserl...@macports.org > Date: 2013-11-08 06:54:28 -0800 (Fri, 08 Nov 2013) > Log Message: > --- > openssh: update to version 6.4p1 This breaks the +hpn variant. Can you take a look? (I've heard it's being maintained again now, so maybe the relevant patch has already been released?) -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: 'port upgrade foobar' upgrades everything
On 11/07/2013 11:08 PM, Joshua Root wrote: On 2013-11-8 16:26 , Lawrence Velázquez wrote: On Nov 7, 2013, at 11:25 PM, Blair Zajac wrote: I recall that 'port upgrade foobar' would only upgrade foobar It should actually upgrade foobar and foobar's outdated dependencies, unless you pass "-n". but it seems that recently it'll upgrade everything. This is happening on my PPC PowerBook that is trying to upgrade octave-devel which always fails. Has anybody else seen this? I have not seen it, to my knowledge. Could be rev-upgrade finding that some ports are broken at the end? Yes, thanks, that was it. There was also an octave-devel upgrade at the same time that SuiteSparse was updated. Blair ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: @macports.org handle
On 2013-11-07 19:47, Lawrence Velázquez wrote: > On Nov 7, 2013, at 12:46 PM, David Strubbe wrote: > >> The guide says: >> >> "7.3. Port Update Policies >> >> Port maintainers normally are given commit privileges to the Subversion >> repository so they can make updates to their own ports." >> >> I suggest that be clarified if more conditions apply. > > Those conditions are described elsewhere in the Guide. > > http://guide.macports.org/chunked/project.membership.html I added a cross-reference to make it more obvious. http://trac.macports.org/changeset/113083 Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
