How identify and remove leftover files on buildbots?
Thomas Friedrichsmeier
thomas.friedrichsmeier at ruhr-uni-bochum.de
Mon Nov 3 08:56:18 PST 2014
Hi,
On Monday 03 November 2014 15:50:24 Rainer Müller wrote:
> > I do not know, whether all files in these directories are unregistered, or
> > only some. But all files in these two directories clearly belong to the
> > rkward port.
>
> It seems like the port writes directly to the target location instead of
> using the destroot directory. This usually happens if the port does not
> respect the DESTDIR=... argument passed to 'make install'.
yes. Only it is what happened in the past. And now the files in question
are destrooted, and thus part of the image (as can also be seen in the
buildbot's log). And that's why port refuses to activate the image: Some files
contained in it are already present at the target location (unregistered).
The question at hand is how to get rid of the files that have been installed
without being registered _previously_.
Regards
Thomas
P.S.: Some more clarification: I am not a regular mac or macports user (pretty
much only for porting RKWard), and so I'm not up to speed on all this.
However, I am both upstream author, and the debian package maintainer of
rkward, and so I do know first-hand that rkward's "make install" is designed
to respect DESTDIR argument. Apparently there used to be a bug (now fixed) in
either cmake, or R, or something else, that caused the files to be mis-
installed to the system path, anyway, or not registered for any other reason.
RKWard's upstream installation procedure has not changed in three years, with
respect to these files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20141103/68098c68/attachment-0001.sig>
More information about the macports-dev
mailing list