On Wed, 20 Aug 2014 17:44:00 +0200, Max Horn <m...@quendi.de> wrote:
Hi,
>
> On 19.08.2014, at 19:57, Daniel Macks <dma...@netspace.org> wrote:
>
> > On Tue, 19 Aug 2014 13:47:58 +0200, Max Horn <m...@quendi.de> wrote:
>
> [...]
>
> >>  cp: /sw/share/info/dir.bak: Permission denied
> >> >> I think this is caused by the install-info tool and the fact 
> that the >> affected packages (e.g. grep) use the "InfoDocs" fields. 
> I don't >> think a package author can do much about that, can they? 
> As such, >> perhaps you could check if the above line is the only one 
> with >> "permission denied", and in that case, demote the "failure" 
> to a >> "warning" ?
> > > In a packaging context, install-info should be deferred to the 
> actual > live install (.deb -> %p) rather than during the writing to 
> the staging > directory (InstallScript -> %i). InfoDocs automatically 
> does the > former. Some build systems automatically disable 
> install-info in the %i > context, but others need to be disabled 
> explicitly by the maintainer. > It's always doable, but there are 
> many variations among the build tools > (sometimes an autoconf flag, 
> sometimes a make variable, sometimes > manually commenting out part 
> of a makefile). Any hints on how to do that, or perhaps examples of 
> packages that do that?
> Many of the affected cases are actually straight GNU packages, such as
> diffutils, gawk, grep, gzip, sed

I just looked at grep, which appears to use a standard automake recipe 
that can be controlled by:

-make install DESTDIR=%d
+make install DESTDIR=%d AM_UPDATE_INFO_DIR=no

dan

  --
Daniel Macks
dma...@netspace.org



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to