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,
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
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
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),
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
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
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
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
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
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
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
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
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
13 matches
Mail list logo
