Re: remove old installations
I think there should be a policy change here. As it seems it is causing more work than it saves doing unclean builds. We could just simply add a option -u for unclean for those that need it. regards Keith. Am 02.12.2011 um 03:30 schrieb Ryan Schmidt: On Dec 1, 2011, at 18:11, Roger Pack wrote: Maybe what it could do it warn when it's doing a dirty installation, so that it's clearer more quickly why something may have failed (i.e. you see $ port install xxx warning: installing over a previous installation ... fetch failed please check your log (it's more immediately obvious *why* the fetch may have failed). That's an idea... we do certainly get dozens of tickets filed per week with main.logs attached that were not from clean build attempts, and are thus often useless, and we waste time explaining this to each reporter and ask them to clean and try again. My suggestion is that instead of always warning at the beginning of unclean builds (since the reason we allow unclean builds at all is that often they'll work just fine), we should modify the error message printed if an error does end up occurring after an unclean build. Currently we always print: Log for foo is at: /opt/local/var/macports/logs/_path_to_foo/foo/main.log Error: Status 1 encountered during processing. To report a bug, see http://guide.macports.org/#project.tickets I claim we should print that only if it was a clean build. If it was not a clean build, we should print: Log for foo is at: /opt/local/var/macports/logs/_path_to_foo/foo/main.log Error: Status 1 encountered during processing. Clean and try again before considering reporting this as a bug. This would also cut down on the so far 28 known duplicates of 29223, though we should really fix that properly as well. https://trac.macports.org/ticket/29223 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
The idea seems to be to automatically clean the work directory before
performing a fetch. That's pretty nonstandard MacPorts behavior though, if I'm
not mistaken.
vq
On Dec 1, 2011, at 2:48 a.m., Ryan Schmidt wrote:
On Dec 1, 2011, at 00:50, Roger Pack wrote:
I was attempting to add this line to a Port:
fetch {
system rm -rf ${worksrcpath}
Why in the world.?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Fwd: remove old installations
Accidentally privately replied LOL. -- Forwarded message -- The idea seems to be to automatically clean the work directory before performing a fetch. That's pretty nonstandard MacPorts behavior though, if I'm not mistaken. I guess the frustration is that if I ever have an aborted installation, with that particular port, and then attempt a reinstall, I am greeted by an obscure error message fetch failed, please consult this log (even if --force is used), so I'm trying to work around that. Most ports reinstall fine over aborted installations, but not this one. -roger- ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
On 1/12/11 22:48, Roger Pack rogerdpa...@gmail.com wrote: I guess the frustration is that if I ever have an aborted installation, with that particular port, and then attempt a reinstall, I am greeted by an obscure error message fetch failed, please consult this log (even if --force is used), so I'm trying to work around that. Most ports reinstall fine over aborted installations, but not this one. -roger- It's regular practise. In nearly all cases with *nix it's: ./configure make make install if you don't succeed you perform either: make uninstall or make clean before you try installing again. Cheers, Phil... -- Nothing to see here... move along, move along ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
Perhaps this is terribly naive: what about sudo port clean --all portname ? On Dec 1, 2011, at 18:22 , Phil Dobbin wrote: On 1/12/11 22:48, Roger Pack rogerdpa...@gmail.com wrote: I guess the frustration is that if I ever have an aborted installation, with that particular port, and then attempt a reinstall, I am greeted by an obscure error message fetch failed, please consult this log (even if --force is used), so I'm trying to work around that. Most ports reinstall fine over aborted installations, but not this one. -roger- It's regular practise. In nearly all cases with *nix it's: ./configure make make install if you don't succeed you perform either: make uninstall or make clean before you try installing again. Cheers, Phil... -- Nothing to see here... move along, move along ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
Perhaps this is terribly naive: what about sudo port clean --all portname Yes that does it. Maybe what it could do it warn when it's doing a dirty installation, so that it's clearer more quickly why something may have failed (i.e. you see $ port install xxx warning: installing over a previous installation ... fetch failed please check your log (it's more immediately obvious *why* the fetch may have failed). -r ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
Why does it need to fetch again if it's already got the file? Scott On Thu, Dec 1, 2011 at 4:11 PM, Roger Pack rogerdpa...@gmail.com wrote: Perhaps this is terribly naive: what about sudo port clean --all portname Yes that does it. Maybe what it could do it warn when it's doing a dirty installation, so that it's clearer more quickly why something may have failed (i.e. you see $ port install xxx warning: installing over a previous installation ... fetch failed please check your log (it's more immediately obvious *why* the fetch may have failed). -r ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
Why does it need to fetch again if it's already got the file? it's an svn checkout and not smart enough to know how :) (see mplayer-devel Portfile) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
On Dec 1, 2011, at 16:48, Roger Pack wrote: I guess the frustration is that if I ever have an aborted installation, with that particular port, What is that particular port, by the way? and then attempt a reinstall, I am greeted by an obscure error message fetch failed, please consult this log (even if --force is used), so I'm trying to work around that. Only if the attempt failed in the fetch phase. Many ports would experience this problem in that case. Clean and try again. (No need to clean --all, just a regular clean to delete the work area is sufficient.) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
On Dec 1, 2011, at 18:11, Roger Pack wrote: Maybe what it could do it warn when it's doing a dirty installation, so that it's clearer more quickly why something may have failed (i.e. you see $ port install xxx warning: installing over a previous installation ... fetch failed please check your log (it's more immediately obvious *why* the fetch may have failed). That's an idea... we do certainly get dozens of tickets filed per week with main.logs attached that were not from clean build attempts, and are thus often useless, and we waste time explaining this to each reporter and ask them to clean and try again. My suggestion is that instead of always warning at the beginning of unclean builds (since the reason we allow unclean builds at all is that often they'll work just fine), we should modify the error message printed if an error does end up occurring after an unclean build. Currently we always print: Log for foo is at: /opt/local/var/macports/logs/_path_to_foo/foo/main.log Error: Status 1 encountered during processing. To report a bug, see http://guide.macports.org/#project.tickets I claim we should print that only if it was a clean build. If it was not a clean build, we should print: Log for foo is at: /opt/local/var/macports/logs/_path_to_foo/foo/main.log Error: Status 1 encountered during processing. Clean and try again before considering reporting this as a bug. This would also cut down on the so far 28 known duplicates of 29223, though we should really fix that properly as well. https://trac.macports.org/ticket/29223 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
remove old installations
Hello all.
I was attempting to add this line to a Port:
fetch {
system rm -rf ${worksrcpath}
however it doesn't seem to work as I would have expected it to (to
clean up that directory).
Error: Target org.macports.fetch returned: bad option rm -rf
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mplayer-devel/mplayer-devel/work/trunk
Any pointers for me on it?
Thanks.
-r
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
On Dec 1, 2011, at 7:50 AM, Roger Pack wrote:
system rm -rf ${worksrcpath}
Why do you need it at all?
A port clean should take care of that...
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: remove old installations
On Dec 1, 2011, at 00:50, Roger Pack wrote:
I was attempting to add this line to a Port:
fetch {
system rm -rf ${worksrcpath}
Why in the world.?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
