[MacPorts] #19430: [port base] port build standalone binaries pkg / dmg
MacPorts
noreply at macports.org
Mon Apr 27 00:36:49 PDT 2009
#19430: [port base] port build standalone binaries pkg / dmg
-------------------------------------------+--------------------------------
Reporter: andre.mueller@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone: MacPorts Future
Component: base | Version: 1.7.1
Keywords: | Port:
-------------------------------------------+--------------------------------
Comment(by andre.mueller@…):
Replying to [comment:1 jmr@…]:
> So what does happen when you run `port mpkg` or `port mdmg`? They both
seem to work as expected here.
Hello
Thank you for your answer. Running "port mdmg" or "port mpgk" does create
the package as without the "m" prefix, but the needed lib under
"/opt/local/lib/" are not included in the standalone package. For example
for the port "logrotate" three libs are needed "libgd, ibpopt and a third
one I do not remember". Creating the port "webalizer" with "port dmg" or
"port mdmg" are different in the sense, that "port mdmg" does include
"X11" files but both do lack the libs. I have also unpacked manually (with
"show package content" and unpacked the Archiv.pax) the packages but they
do really not include the libs. Pleas find the dmg for the port
"logrotate" created with "port mdmg logrotate". Installing this
"standalone" package on a system without a macports installation and by
running the port, the port will abort with an error message, that it could
not open the referenced lib ... under /opt/local/lib/ - that is obvious as
the installation of the standalone package does neither create this
directory nor put there the needed libs.
With best regards,
André
--
Ticket URL: <http://trac.macports.org/ticket/19430#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list