https://bugzilla.novell.com/show_bug.cgi?id=469178 User lehrig@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=469178#c2 --- Comment #2 from Rainer Lehrig 2009-01-25 01:47:54 MST --- (1) I added %fdupes $RPM_BUILD_ROOT to the spec file but get error: line 25: Unknown tag: %fdupes $RPM_BUILD_ROOT Have i mistyped something ? (2) Of course we could place the lib in /usr/lib but i think symbolic linking is better, because we provide an optional software under /opt Everything from us goes to /opt/ourproject If every optional software would place it's libs etc. somewhere under /usr the system disk might get full. But if you place the files under /opt/package you can mount opt on a separate disk and thus avoid filling the system disk. Again, within our spec file we have these lines: %__ln_s /opt/pvb/rllib/lib/librllib.so.1.0.0 %{buildroot}/usr/lib/librllib.so %__ln_s /opt/pvb/rllib/lib/librllib.so.1.0.0 %{buildroot}/usr/lib/librllib.so.1 %__ln_s /opt/pvb/rllib/lib/librllib.so.1.0.0 %{buildroot}/usr/lib/librllib.so.1.0 %__ln_s /opt/pvb/rllib/lib/librllib.so.1.0.0 %{buildroot}/usr/lib/librllib.so.1.0.0 and %postin /sbin/ldconfig %postun /sbin/ldconfig Could you please think about my arguments and eventually disable this check and allow what we are doing ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469178 User lehrig@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=469178#c4 --- Comment #4 from Rainer Lehrig 2009-01-25 04:02:31 MST --- (1) This is a fuzz :-( On some distries i get: expansion error nothing provides fdupes And on factory opensuse i get an error when using BuildRequires: fdupes %fdupes %{buildroot} or must i really write ? %fdupes $RPM_BUILD_ROOT (2) /etc/ld.so.conf.d/pvbrowser this is in principle possible, but i'm tied of all what i MUST change from version to version :-( Here to show why this is not so easy for us: Our project http://pvbrowser.org is a framework for creating SCADA apps. Our users already have a lot of qmake *.pro files in use. They will NOT want to change all these, when the admins of opensuse come around with new rules for the buildservice. Here is an example pro file (notice that we do not only support linux) ###################################################################### # generated by pvdevelop at: Di Jan 13 11:28:13 2009 ###################################################################### TEMPLATE = app CONFIG = warn_on release CONFIG -= qt # Input HEADERS += pvapp.h \ mask5_slots.h \ mask4_slots.h \ mask3_slots.h \ mask2_slots.h \ mask1_slots.h SOURCES += main.cpp \ mask5.cpp \ mask4.cpp \ mask3.cpp \ mask2.cpp \ mask1.cpp !macx { unix:LIBS += /usr/lib/libpvsmt.so -pthread #unix:LIBS += /usr/lib/libpvsid.so unix:INCLUDEPATH += /opt/pvb/pvserver unix:LIBS += /usr/lib/librllib.so unix:INCLUDEPATH += /opt/pvb/rllib/lib } macx:LIBS += /opt/pvb/pvserver/libpvsmt.a /usr/lib/libpthread.dylib #macx:LIBS += /opt/pvb/pvserver/libpvsid.a macx:INCLUDEPATH += /opt/pvb/pvserver macx:LIBS += /usr/lib/librllib.dylib macx:INCLUDEPATH += /opt/pvb/rllib/lib win32-g++ { win32:LIBS += $(PVBDIR)/win-mingw/bin/librllib.a win32:LIBS += $(PVBDIR)/win-mingw/bin/libserverlib.a $(MINGWDIR)/lib/libws2_32.a $(MINGWDIR)/lib/libadvapi32.a win32:INCLUDEPATH += $(PVBDIR)/pvserver win32:INCLUDEPATH += $(PVBDIR)/rllib/lib } else { win32:LIBS += $(PVBDIR)/win/bin/serverlib.lib wsock32.lib advapi32.lib win32:INCLUDEPATH += $(PVBDIR)/pvserver win32:LIBS += $(PVBDIR)/win/bin/rllib.lib win32:INCLUDEPATH += $(PVBDIR)/rllib/lib } #DEFINES += USE_INETD TARGET = pvs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469178 User lehrig@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=469178#c6 --- Comment #6 from Rainer Lehrig 2009-01-25 23:33:32 MST ---

hmm, fdupes is on the newer SUSE ones, perhaps not on the older. Yes, definitely

hmm, I think you can leave the symlinks, but perhaps let the ldconfig some run. Could i use /sbin/ldconfig our_directory or /sbin/ldconfig -l our_library additional to the normal /sbin/ldconfig in order to satisfy the check ? Would the check even notice that ? Would we get a conflict, when ldconfig sees our library in 2 places (/usr/lib AND /opt/our_project) ?

In my opinion it would be better to omit this check at all !!! Is there an option to instruct the checker not to do that check ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469178 User adrian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469178#c8 Adrian Schröter changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #8 from Adrian Schröter 2009-02-26 03:55:21 MST --- Sorry, but bugzilla is not a support tool, it is a bugreport system. I do not see any Build Service bug in this report, please go to the mailing lists for support. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.