Re: Building root fails
Please provide some details, in a bug report (not here). Chris On 11 Mar 2012, at 2:58am, Rodolfo Aramayo wrote: FYI..I have uninstalled glew and tried to rebuild root, but this did not work On Fri, Mar 9, 2012 at 14:02, Chris Jones jon...@hep.phy.cam.ac.uk wrote: Hi, It appears that despite the fact root has been told to use its own built in glew, it still uses the macports one and this causes problems. Just to clarify the above point a little. The issue is not just if you have GLEW installed, but if you have glew installed without the X11 variant enabled (which is not the default). Chris smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
npm permissions error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, all.
I'm using npm to install something from npmjs.org even though I'm
using sudo I'm getting:
`npm ERR! Error: EPERM, operation not permitted '/opt/local/bin/npm'
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR!
npm ERR! System Darwin 10.8.0
npm ERR! command /opt/local/bin/node
/private/var/folders/QU/QUp3HUtzF3qX4y3OTcpg7E+++TM/-Tmp-/npm.50667/package/cli.js
install -gf
npm ERR! cwd
/private/var/folders/QU/QUp3HUtzF3qX4y3OTcpg7E+++TM/-Tmp-/npm.50667/package
npm ERR! node -v v0.6.12
npm ERR! npm -v 1.1.4
npm ERR! path /opt/local/bin/npm
npm ERR! code EPERM
npm ERR! message EPERM, operation not permitted '/opt/local/bin/npm'
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!
/private/var/folders/QU/QUp3HUtzF3qX4y3OTcpg7E+++TM/-Tmp-/npm.50667/package/npm-debug.log
npm not ok
It failed`
Any ideas on why /opt/local/bin is denying me access?
Cheers,
Phil...
- --
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.
Wm. Shakespeare - Much Ado About Nothing
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPXRABAAoJEKpMeDHWT5ADph0H/2NWgPiCYMPcsDQdbHApnLyw
uiJ1usE9Xe5G/OIc4S8C+xX1hvmth9E4iYi+rIHHrv7ogLBhQd8JVOXJEViaVeXP
Eh0SsxFknnisKzqpYc7nT1T+6DnTWUNVgvoMt0epzD18JmPforMauPbZ6HIQ/Qxa
1cTwM0hQGIqLWJRz95/UZy9jHzIbLsWpEH9Si6SrUV0eVSPMlyryY+SjUSysCi19
J4eCkvQHa7q2HhNGM5wREzeGorfowR0Z/L7ehR6UzZ+OJ5gCemmbIkoiK/VMPdEu
2442F+PMa6+lA0R2wrnpXalPymcN21dH0C8St2EpVcvQRQcK+GFumoNZftXMXDM=
=z+g8
-END PGP SIGNATURE-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: npm permissions error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2012 20:50, Phil Dobbin wrote: I'm using npm to install something from npmjs.org even though I'm using sudo I'm getting: [snip] Scrub that. I figured it out. Sorry for the noise, Phil... -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPXRKXAAoJEKpMeDHWT5ADyPYH/jLnWmH9d5ptl/KUVJ0ycnsF vAptJkecrAwMZ1WgdBYtOl7JB5+SgRJ7iPz6nGC3QIjhmI8Tcrlj7zcMS6GPtihX SuP8TczCoGSsO3XFErZdtGHP9ic7Lw2kqODDZlteQD5McuAqrn8V/7ALHGino0Bz WTyLk6qg9x+ufUtAOSltDrt5CGcnd6MyNPQT7Ih9HXPCLOR90uPfVhqVTBFdZx5k /mFTV2AJM+DPiPMUX4dCTlwa2SL3PHg71gzdV2VIoEYuOv7p7rmsszhZsh5qZsjl lTXOCfS0lktSiBV7myrOCcwLVNUAZc6BeKGpEuTNGZ1tDSSC9jfJeFluqQgZ6bo= =DzQE -END PGP SIGNATURE- ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: npm permissions error
On Mar 11, 2012, at 16:01, Phil Dobbin wrote: On 11/03/2012 20:50, Phil Dobbin wrote: I'm using npm to install something from npmjs.org even though I'm using sudo I'm getting: [snip] Scrub that. I figured it out. What was the solution? You shouldn't be using sudo with npm. npm is for installing node modules locally. Projects that recommend the use of npm -g for a global install should instead have an entire MacPorts port made for them. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
How to install qt4-mac and qt3-mac ?
Hi everyone, Is there a way to make qt4-mac and qt3-mac package installed on the same system ? I have the following message : Error: Unable to execute port: Can't install qt3-mac because conflicting ports are installed: qt4-mac I need to have both on my system, is it possible with the macports ? Regards, -- Alexandre Parent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install qt4-mac and qt3-mac ?
On Mar 11, 2012, at 4:15 PM, Alexandre Parent wrote: Hi everyone, Is there a way to make qt4-mac and qt3-mac package installed on the same system ? I have the following message : Error: Unable to execute port: Can't install qt3-mac because conflicting ports are installed: qt4-mac I need to have both on my system, is it possible with the macports ? Not in the same prefix. What is your need for need qt3-mac? Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install qt4-mac and qt3-mac ?
On 12/03/12 00:19, Bradley Giesbrecht wrote: Not in the same prefix. What is your need for need qt3-mac? Regards, Bradley Giesbrecht (pixilla) I need to compile/resurrect an old project of mine, and it use qt3. -- Alexandre Parent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: npm permissions error
On Mar 11, 2012, at 18:36, Jeremy Lavergne wrote: Projects that recommend the use of npm -g for a global install should instead have an entire MacPorts port made for them. Why not have MacPorts interface directly with npm, and let it do the node package managing? We shouldn't be in the business or adding portfiles for other package manages when they work just fine being controlled by MacPorts. Only if they have problems should MacPorts step in with its own portfiles. But we are in the business of adding portfiles for software in other package managers. We already do exactly that for perl (cpan), php (pear, pecl), etc. We don't want other package managers installing software into the MacPorts prefix, but that's exactly what npm -g (and cpan and pear and pecl) would do. That's why the npm port already prints a message explaining to users that the use of npm -g is discouraged. We already have ports for some things you can install with npm -g, like jake and coffee-script. We should continue adding ports for other such software until nobody feels a need to run npm -g. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: npm permissions error
But we are in the business of adding portfiles for software in other package managers. We already do exactly that for perl (cpan), php (pear, pecl), etc. We don't want other package managers installing software into the MacPorts prefix, but that's exactly what npm -g (and cpan and pear and pecl) would do. That's why the npm port already prints a message explaining to users that the use of npm -g is discouraged. We already have ports for some things you can install with npm -g, like jake and coffee-script. We should continue adding ports for other such software until nobody feels a need to run npm -g. Why is MacPorts not actually controlling all these underling package managers? why can't we have MacPorts itself running 'npm -g' and tracking files from there? smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
gnuplot: question about wxWidgets(-devel) Universal variants
Hello,
I would like to use gnuplot with wxt terminal (wxWidgets). The current
Portfile uses
variant wxwidgets description Enable wxWidgets front-end {
depends_lib-append port:wxWidgets
configure.args-delete --disable-wxwidgets
configure.args-append --with-wx-config=${prefix}/bin/wx-config
}
if {[variant_isset wxwidgets]} {
# wxWidgets is not universal and is 32-bit only
universal_variant no
supported_archs i386 ppc
}
however wxWidgets 2.8 only support Carbon (= only ppc and i386). I
have tried to modify the gnuplot's Portfile to use wxWidgets 2.9. The
following code works for me (Lion x86_64):
variant wxwidgets description Enable wxWidgets front-end {
depends_lib-append port:wxWidgets-devel
configure.args-delete --disable-wxwidgets
configure.args-append --with-wx-config=${prefix}/bin/wx-config
}
if {[variant_isset wxwidgets]} {
if {${configure.compiler} == clang} {
configure.compiler llvm-gcc-4.2
}
}
but since many other ports depend on wxWidgets (conflicting with
wxWidgets-devel), it might be undesirable to put the code above to
gnuplot's Portfile. Also, for anyone using ppc or i386 the version 2.8
of wxWidgets might be perfectly OK.
How exactly should the code be written to enable compiling 64-bit
version of gnuplot with wxt terminal, without interfering with other
ports and without breaking functionality for 32-bit architectures?
Once/if that question is answered, I have a Portfile for the new
gnuplot 4.6 ready to be committed.
Thank you,
Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: npm permissions error
On Mar 11, 2012, at 18:47, Jeremy Lavergne wrote: But we are in the business of adding portfiles for software in other package managers. We already do exactly that for perl (cpan), php (pear, pecl), etc. We don't want other package managers installing software into the MacPorts prefix, but that's exactly what npm -g (and cpan and pear and pecl) would do. That's why the npm port already prints a message explaining to users that the use of npm -g is discouraged. We already have ports for some things you can install with npm -g, like jake and coffee-script. We should continue adding ports for other such software until nobody feels a need to run npm -g. Why is MacPorts not actually controlling all these underling package managers? why can't we have MacPorts itself running 'npm -g' and tracking files from there? Are we talking about something like an npm portgroup with which we could easily whip out ports for each globally-installable npm package? Or modifications to MacPorts base to directly run npm without needing a portfile? The problem with trying to write an npm portgroup is that there are many things that package managers do that are perfectly fine to do when users control them directly but that we wouldn't want them to do when MacPorts controls them. Some examples from npm (pear, pecl, cpan probably are similar): npm installs the latest version; we want to install a specific version. Maybe there's a way to tell it what version to use. npm installs directly to its destination, without using a destroot, so we can't track the files it installs. Maybe there's a way to tell it to use a destroot. npm downloads files on its own, so we don't get the chance to verify the files' integrity or to mirror them. port fetch on some port using this hypothetical npm portgroup would not actually fetch anything; it would fetch during the build phase, which users would not unexpect. Maybe there's a way to tell it to use an already-downloaded distfile. npm handles dependencies; we want to handle dependencies in MacPorts. npm is unique (as compared with cpan, pear, pecl) in that it allows multiple copies of modules to be installed, in different versions, in different hierarchies. So an npm package foo could depend on version 0.2 of bar and package baz could depend on version 0.4 of bar and npm automatically handles installing them in different directories. npm only handles npm dependencies, but many npm modules require other compiled libraries, which must already be installed; we need to be able to specify those. This kind of thing was discussed before for cpan, and again for pecl, and again for pear; the recognition of these various issues is what led Bradley to recently commit hundreds of ports for all the packages available in pear. Regarding the other idea of having MacPorts directly run npm without needing even a portfile, we would still have the above problems, plus the effort of integrating into base, with the end result that the user has fewer assurances about the software than the few they already have with most other ports. In MacPorts, we at least guarantee users that one other person has confirmed that a port can be installed somewhere. If we were to directly call npm and bypass that approval process, there would be no guarantee at all. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gnuplot: question about wxWidgets(-devel) Universal variants
On Mar 11, 2012, at 18:51, Mojca Miklavec wrote:
I would like to use gnuplot with wxt terminal (wxWidgets). The current
Portfile uses
variant wxwidgets description Enable wxWidgets front-end {
depends_lib-append port:wxWidgets
configure.args-delete --disable-wxwidgets
configure.args-append --with-wx-config=${prefix}/bin/wx-config
}
if {[variant_isset wxwidgets]} {
# wxWidgets is not universal and is 32-bit only
universal_variant no
supported_archs i386 ppc
}
however wxWidgets 2.8 only support Carbon (= only ppc and i386). I
have tried to modify the gnuplot's Portfile to use wxWidgets 2.9. The
following code works for me (Lion x86_64):
variant wxwidgets description Enable wxWidgets front-end {
depends_lib-append port:wxWidgets-devel
configure.args-delete --disable-wxwidgets
configure.args-append --with-wx-config=${prefix}/bin/wx-config
}
if {[variant_isset wxwidgets]} {
if {${configure.compiler} == clang} {
configure.compiler llvm-gcc-4.2
}
}
but since many other ports depend on wxWidgets (conflicting with
wxWidgets-devel), it might be undesirable to put the code above to
gnuplot's Portfile. Also, for anyone using ppc or i386 the version 2.8
of wxWidgets might be perfectly OK.
How exactly should the code be written to enable compiling 64-bit
version of gnuplot with wxt terminal, without interfering with other
ports and without breaking functionality for 32-bit architectures?
Once/if that question is answered, I have a Portfile for the new
gnuplot 4.6 ready to be committed.
The simplest solution for us would be for the developers of wxWidgets to
finally release a stable 64-bit compatible version of their software. Then we
could update the wxWidgets portfile to that version and remove all the 32-bit
forcing in all the ports that do that.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
