file conflicts, how do you think which files are worth removing?
Kok, Auke
sofar at foo-projects.org
Mon Jun 2 19:42:31 CEST 2008
Zbigniew Luszpinski wrote:
> Saturday 31 of May 2008 19:19:21 Zbigniew Luszpinski wrote:
>
> Just some comments from me
>
>> openMotif:/usr/bin/column
>> util-linux:/usr/bin/column
>
> block column installation at openMotif?
definately
>> rpm:/usr/bin/rpm2cpio
>> rpmunpack:/usr/bin/rpm2cpio
>
> rpmunpack has one additional exec: rpmunpack
> rpm module installs much more but not rpmunpack.
> Mark'em as conflicting?
yep. this is obvious (maybe painful, because it breaks things like j2sdk which are
shipped in rpm form only and lunar needs rpmunpack to open it)
>> firefox:/opt/lunar/plugins/libnullplugin.so
>> seamonkey:/opt/lunar/plugins/libnullplugin.so
>> firefox:/opt/lunar/plugins/libunixprintplugin.so
>> seamonkey:/opt/lunar/plugins/libunixprintplugin.so
>
> This can be resolved at module install stage:
> if files exist do not overwrite'em fi;
that's ok, these are NULL plugins anyway. and seamonky is not stable anyway
>> libXpm:/usr/bin/cxpm
>> xpm:/usr/bin/cxpm
>> libXpm:/usr/bin/sxpm
>> xpm:/usr/bin/sxpm
>> libXpm:/usr/include/X11/xpm.h
>> xpm:/usr/include/X11/xpm.h
>
> libXpm installs everything what xpm installs plus some more.
> Remove xpm module?
if you fix emacs, icewm, emacs-cvs (they depend on xpm).
Auke
More information about the Lunar-dev
mailing list