On Sunday 02 September 2007 18:00:21 wrote Marcus Rueckert: > On 2007-09-02 16:22:58 +0200, Stephan Kulow wrote: > > Am Friday 24 August 2007 schrieb Vladimir Nadvornik: > > > On středa 16 květen 2007, Stephan Kulow wrote: > > > > It's pretty simple: BuildRequire fdupes and then use "%fdupes > > > > $RPM_BUILD_ROOT" in your install section. This will check for > > > > duplicated files and make them hardlink. Just be careful that these > > > > duplicated files do not end up in different subpackages - I haven't > > > > tried what rpm does in that case. > > > > > > There seems to be another problem. %fdupes can create hardlinks between > > > files that would finally end on different partitions. > > > See > > > https://bugzilla.novell.com/show_bug.cgi?id=304167 > > > > > > Using something like > > > %fdupes $RPM_BUILD_ROOT/usr > > > %fdupes $RPM_BUILD_ROOT/srv > > > ... > > > > > > fixes the problem. > > > > > > Do you think that the %fdupes macro should be changed to do this > > > automatically? > > > > I think it would be logical to make this automatic. > > and it would be still broken. you can not assume that hardlinks between > different directories will _always_ work. the only place where you can > say "it wont break anything" are hardlinks in the same directory. > anything else can be on a different partition. that said i think the > best would be to patch fdupes and let it use hardlinks for any > duplicates in the same directory, but symlinks for anything else.
That is right, but what happens acctually when you have different partitions ? Does rpm fail to install the package or does it create a full copy of the file on the other partition ? If it is the later, I think hardlinks are okay to use .. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
