|
From: Jan K. <rcp...@ja...> - 2003-11-07 16:33:55
|
Hi, Nice merge, Anton. Here is attached the patch for 200311071017 snapshot to introduce --disable-gnome-vfs Omit Gnome-VFS-2.0 'libntfs' interface (default=detect) --enable-gnome-vfs emits error if the compilation is not possible (used by rpm .spec file). The default behaviour of Gnome-VFS autodetection therefore does not introduce any new requirements for ntfsprogs .tar.gz package compilation. (Patch also removes unneeded 'AC_PROG_CXX' as besides threads I hate C++.) On Fri, 07 Nov 2003 10:37:30 +0100, Anton Altaparmakov wrote: ... > At present, I have made the rpm build process split off an > ntfsprogs-gnomevfs rpm which contains the module and the config file for > it. The rpm is dependent on the installation of the main ntfsprogs rpm. You specified a zillion of 'Requires'. I use and expect there should be listed only the packages explicitely required by this package as all the other packages/libraries dependent transitively will get resolved during the final user RPM installation and/or autodetected during the RPM build. Another 'Requires' issue is whether to list just the '.so.0' dependencies or whether to list the whole packages containing them. I list the packages containing them although it may vary a bit for different vendors (such as Mandrake). I would use for ntfsprogs-gnomevfs: BuildRequires: glib2-devel Requires: glib2 BuildRequires: gnome-vfs2-devel Requires: gnome-vfs2 > However the dependencies are still just as mad for the main rpm. The > build process needs cleaning up for that so that all the gnome/glib stuff > only gets added to the compilation of the libntfs-gnomevfs related > sources... I do not see this behaviour - my test build of RPM lists only the proper (and non-transitive) library dependencies by 'rpm -qRp ntfsprogs-X.i386.rpm'. Regards, Lace -- Jan Kratochvil; Captive: free r/w NTFS Filesystem; http://www.jankratochvil.net/ |
