[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: build-depend on doc packages?



Hi John!

Em Dom, 2009-11-22 às 08:53 -0800, John MacFarlane escreveu:
(...) 
> One question that has come up is this:
> In building pandoc's documentation, Haddock warns:
> 
> > Warning: The documentation for the following packages are not installed. No   
> > links will be generated to these packages: array-0.2.0.0, base-4.1.0.0,       
> > bytestring-0.9.1.4, containers-0.2.0.1, directory-1.0.0.3, filepath-1.1.0.2,  
> > ghc-prim-0.1.0.0, integer-0.1.0.1, old-locale-1.0.0.1, old-time-1.0.0.2,      
> > packedstring-0.1.0.1, pcre-light-0.3.1, pretty-1.0.1.0, process-1.0.1.1,      
> > rts-1.0, syb-0.1.0.1, template-haskell-2.3.0.1, unix-2.3.2.0 
> 
> It produces the documentation just fine, but without the hyperlinks to
> these other packages' documentation. If make the relevant -doc packages
> build-depends, Haddock will add the hyperlinks, but users may find that
> they don't lead anywhere if they haven't installed the -doc packages
> that are linked to.  We could ensure that there are no broken links by
> making all these -doc packages not just build-depends but
> install-depends of libghc6-pandoc-doc.  But I can imagine someone
> wanting the pandoc documentation without all the other stuff.  So, is
> there a policy about this?  Should we go for
> 
> 1) no hyperlinks,
> 2) hyperlinks that will be broken unless other -doc packages are
> installed, or
> 3) hyperlinks that are guaranteed not to be broken, because the
> other -doc packages are install-depends?

The option I use is the 2nd, but the other -doc packages are Recommends.
Notice that dh_haskell_depends will create the ${haskell:Recommends}
variable if you wish to use it, so it's kind of the policy.

> There's another warning we're getting in the build process that I
> don't understand:
> 
> > Linking debian/dh_haskell_shlibdeps/a.out ...                                 
> > dpkg-shlibdeps: warning: binaries to analyze should already be installed in   
> > their package's directory.                                                      
> > dpkg-shlibdeps: warning: dependency on libdl.so.2 could be avoided if         
> > "debian/dh_haskell_shlibdeps/a.out" were not uselessly linked against it (they  
> > use none of its symbols).                                                       
> > dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if          
> > "debian/dh_haskell_shlibdeps/a.out" were not uselessly linked against it (they  
> > use none of its symbols).                                                       
> > dpkg-shlibdeps: warning: dependency on libutil.so.1 could be avoided if       
> > "debian/dh_haskell_shlibdeps/a.out" were not uselessly linked against it (they  
> > use none of its symbols).                                                       
> > dpkg-shlibdeps: warning: dependency on libpcre.so.3 could be avoided if       
> > "debian/dh_haskell_shlibdeps/a.out" were not uselessly linked against it (they  
> > use none of its symbols).
> 
> Is this something we should fix?  IF so, how?

No, this is done to generate the libdeps.  Don't worry.

Greetings.

(...)

-- 
marcot
http://marcot.iaaeee.org/



Reply to: