[MacPorts] #45185: lv2 @1.10.0, lilv @0.20.0, serd @0.20.0, sord @0.12.2, sratom @0.4.6: new ports
MacPorts
noreply at macports.org
Sun Sep 28 22:44:18 PDT 2014
#45185: lv2 @1.10.0, lilv @0.20.0, serd @0.20.0, sord @0.12.2, sratom @0.4.6: new
ports
-------------------------------------------------+-------------------------
Reporter: aggraef@… | Owner: devans@…
Type: submission | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.3.1
Resolution: fixed | Keywords: haspatch
Port: lv2core slv2 lv2 lilv serd sord |
sratom |
-------------------------------------------------+-------------------------
Comment (by devans@…):
Replying to [comment:14 aggraef@…]:
> Replying to [comment:11 devans@…]:
> > * updated library dependencies where necessary
>
> Hmm, I messed those up pretty badly, I'm afraid. The way that I'm
testing new ports right now is to put them into my local ports repository
and run `port build portname`. Is it possible to have `port` do this in a
pristine MacPorts environment (kind of chrooted MacPorts installation) so
that I can check the dependencies before the ports are submitted and
checked by the buildbots?
I noticed the issue by running
{{{
sudo port -d configure
}}}
on each port and examining the configure debug messages to see what
dependencies were being checked.
You can simulate the way the buildbots work by doing something like this
{{{
sudo port deactivate active
sudo port configure
}}}
If you don't want to do this in your main MacPorts environment, then you
can install a second (or more) MacPorts installation(s) for testing using
different prefixes. See
[https://guide.macports.org/#installing.macports.source.multiple Install
Multiple MacPorts Copies] in the Guide.
Hope this helps.
--
Ticket URL: <https://trac.macports.org/ticket/45185#comment:15>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list