Hi all,

this was fixed some days ago in trunk and merged into the 7.0 branch
for the release of 7.0 final.

We could indeed make the shared file check optional, for targets that
need it, however this would result in random build results, as depending
on the build order the man page might (or other shared files) might then
contain the content of either the package a or package b. It should
always be favourable to explicitly modify shared files in packages to not
cause conflicts for deterministic build results.

This new error was an unfortunate regression, probably due to a
recent util-linux update.

Yours,

On Sunday 17 February 2008 14:01:41 Mike N wrote:
> 
> Hello,
> 
> Just sending this email to describe a workaround I did to fix minor problem
> in nfs-utils package.
> 
> SVN version (8.0) T2 compilation environment fails to create nfs-utils
> *.tar.bz2 distribution package file even when it succeeds to compile the
> nfs-utils package.
> 
> The error message is "Found shared files with other packages" and
> conflicting file is "/usr/share/man/man5/nfs.5". This man5/nfs.5 file is
> created both in nfs-utils and util-linux packages.
> 
> Well, this error is pretty safe to ignore so I implemented "dirty haxor fix"
> into Build-Pkg script. I simply added piece of code to check that whether
> shared filename is "/usr/share/man/man5/nfs.5" then shared file error is
> simply ignored and package compilation continues as usual. 
> 
> The fix is hard-coded into the Build-Pkg script where it goes this shared
> checking but better way would be to have "target specific" configuration
> option where one could list these "ignore on shared error" file masks.
> 
> Mike

-- 
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  Geschäftsführer: Susanne Klaus, René Rebe
  Sitz: Berlin, Amtsgericht Charlottenburg HRB 105 123 B
  USt-IdNr.: DE251602478
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2

Reply via email to