Re: Struggling with dpkg-buildpackage with kdebase (latest CVS)

2003-12-28 Thread Alan Chandler
On Sunday 28 December 2003 12:13, Achim Bohnet wrote:
>
> Normally KDE docs are installed into /usr/share/doc/kde/HTML (note
> additional kde/ subdir).  HTML dir is one of the dirs where KDEs
> 'everything below one prefix' does not match FHS with prefix set to
> /usr.


> > I wrote ...

> > The relevent piece of makefile in kdebase/admin/Doxyfile.am seems to be
> > the following.
> >
> >
> >if test ! -x $(top_builddir)/apidocs/common; then \
> > if test -d $(top_srcdir)/doc/common; then \
> >common_dir=`cd $(top_srcdir)/doc/common &&
> > pwd` ;\ else \
> >common_dir=$(kde_libs_htmldir)/en/common ;\
> > fi ;\
> > $(LN_S) $$common_dir
> > $(top_builddir)/apidocs/common; \ fi ;\
> >

>
> I had a look at one of my debiandirs files and found only
>
> export kde_htmldir=/usr/share/doc/kde/HTML
> ...
> configkdevelop=...--with-kdelibsdoc-dir=/usr/share/doc/kdelibs3-doc/html...
>

The package that is created is from kdelibs is called kdelibs4-doc - so where 
does your kdelibs3-doc come from?


>
> So kde_libs_htmldir is not set/exported and not defined for configkde.
>
> I've not installed kdelibs3-doc so can't check where it's docs are
> installed. 

As I said above, this is kdelibs4-doc - but it appears to be installed into 
/usr/share/doc/kde/HTML/en

Although I can see the -with-kdelibsdoc-dir=/usr/share/doc/kdelibs3-doc/html 
in the kdelibs/debian/debiandirs file from that package, I don't have 
anything installed there when I install kdelibs4-doc from the .debs that I 
made from kdelibs (or any of the other packages).

>Please check where kdelibs3-doc installs it's docu and add do
> configkde --with-kdelibsdoc-dir=/usr/share/doc/kdelibs?/html.  I guess
> exporting additionaly kde_libs_htmldir in debiandirs does not hurt.

I added something to the kdebase/admin/debianrules file to create those extra 
exports and configkde values
>
> Does this fix the problem?   If yes, kde-common/admin/debianrules needs to
> be updated.

No it doesn't - ther seems to be a problem with the link of something to 
apidocs/common which causes particular files not to exist and give make 
errors.  Here is the snippet of the output around the problem

cd /root/kdebase/obj-i386-linux && \
/usr/bin/make apidox
make[1]: Entering directory `/root/kdebase/obj-i386-linux'
make[2]: Entering directory `/root/kdebase/obj-i386-linux'
*** Creating API documentation main page
Warning: ignoring unsupported tag `ABBREVIATE_BRIEF   =' at line 79, file 
Doxyfile
Warning: ignoring unsupported tag `XML_PROGRAMLISTING =' at line 817, file 
Doxyfile
Error: tag HTML_HEADER: header file `apidocs/common/mainheader.html' does not 
exist
make[2]: Leaving directory `/root/kdebase/obj-i386-linux'
include ../admin/Doxyfile.am
Making apidox in libkonq
make[2]: Entering directory `/root/kdebase/obj-i386-linux/libkonq'
make[3]: Entering directory `/root/kdebase/obj-i386-linux/libkonq'
ln: `../apidocs/common': File exists
Warning: ignoring unsupported tag `ABBREVIATE_BRIEF   =' at line 79, file 
Doxyfile
Warning: ignoring unsupported tag `XML_PROGRAMLISTING =' at line 817, file 
Doxyfile
Error: tag HTML_HEADER: header file `../apidocs/common/header.html' does not 
exist
make[3]: *** [apidox-am-yes] Error 1
make[3]: Leaving directory `/root/kdebase/obj-i386-linux/libkonq'
make[2]: *** [apidox] Error 2
make[2]: Leaving directory `/root/kdebase/obj-i386-linux/libkonq'
make[1]: *** [apidox] Error 1
make[1]: Leaving directory `/root/kdebase/obj-i386-linux'
make: *** [build-stamp] Error 2
kanger:~/kdebase#


-- 
Alan Chandler
[EMAIL PROTECTED]




Re: Struggling with dpkg-buildpackage with kdebase (latest CVS)

2003-12-28 Thread Chris Cheney
On Sun, Dec 28, 2003 at 01:13:56PM +0100, Achim Bohnet wrote:
> The KDEs 'everything below' prefix and the quirks used in debian to follow
> FHS, do not play well together.  Untils we find/agree on an algorithm how
> to handle a KDE installations distrubuted accross
> 
>   a) FHS (easy ;)
>   b) /usr/local
>   c) somewhere else (e.g. /opt or /home/joeUsers/ etc) via KDEDIR(s)
> 
> and patch kstandarddirs.*.in accordingly the KDE dir layout versus FHS
> layout issue will catch us again and again.

As far as I know a) and b) work correctly (I specifically hacked in
/usr/local support myself). I think c) works correctly also when you set
KDEDIRS, but there is a problem some people have with /etc/kderc being
set. It causes the install to also see the FHS and /usr/local files,
which annoys them (iirc).

Chris


signature.asc
Description: Digital signature


Re: Struggling with dpkg-buildpackage with kdebase (latest CVS)

2003-12-28 Thread Achim Bohnet
On Sunday 28 December 2003 11:06, Alan Chandler wrote:
> I am trying to build myself some up to date debs (in a sid chroot inside my 
> existing debian system) 
> 
> The apidocs part is failing - thus.  
> 
> Error: tag HTML_HEADER: header file `../apidocs/common/header.html' does not 
> exist
> make[3]: *** [apidox-am-yes] Error 1
> 
> In checking up, it appears that ../apidocs/common is a unsatisfied link to 
> /usr/share/doc/HTML/en/common  (the HTML directory does not yet exist in my 
Hi Alan,

Normally KDE docs are installed into /usr/share/doc/kde/HTML (note
additional kde/ subdir).  HTML dir is one of the dirs where KDEs
'everything below one prefix' does not match FHS with prefix set to
/usr.

> chroot  - despite having installed kdelibs from the freshly built debs)
> 
> The relevent piece of makefile in kdebase/admin/Doxyfile.am seems to be the 
> following. 
> 
> 
>if test ! -x $(top_builddir)/apidocs/common; then \
> if test -d $(top_srcdir)/doc/common; then \
>common_dir=`cd $(top_srcdir)/doc/common && pwd` ;\
> else \
>common_dir=$(kde_libs_htmldir)/en/common ;\
> fi ;\
> $(LN_S) $$common_dir $(top_builddir)/apidocs/common; \
> fi ;\
> 
> Which sort of makes me think that $(kde_libs_htmldir) is being set to the 
> final target rather than the obj-i386-linux build directory during the 
> building of the debs.  I presume in most peoples case they will have 
> established the /usr/share/docs/HTML hierarchy from previous builds so not 
> noticed the problem.

I had a look at one of my debiandirs files and found only

export kde_htmldir=/usr/share/doc/kde/HTML
...
configkdevelop=...--with-kdelibsdoc-dir=/usr/share/doc/kdelibs3-doc/html...


So kde_libs_htmldir is not set/exported and not defined for configkde.

I've not installed kdelibs3-doc so can't check where it's docs are installed.
Please check where kdelibs3-doc installs it's docu and add do configkde
--with-kdelibsdoc-dir=/usr/share/doc/kdelibs?/html.  I guess exporting
additionaly kde_libs_htmldir in debiandirs does not hurt.

Does this fix the problem?   If yes, kde-common/admin/debianrules needs to
be updated.
 
> I've scouted around the KDE CVS repository looking for recent relevent 
> changes 
> around this area and I can't find any - normally an indication that I am way 
> off beam with my thinking.  Since I am new to this area and on a steep 
> learnign curve, can anyone shortcut this for me and help me understand why it 
> is like the way it is (and what needs to change).

The KDEs 'everything below' prefix and the quirks used in debian to follow
FHS, do not play well together.  Untils we find/agree on an algorithm how
to handle a KDE installations distrubuted accross

a) FHS (easy ;)
b) /usr/local
c) somewhere else (e.g. /opt or /home/joeUsers/ etc) via KDEDIR(s)

and patch kstandarddirs.*.in accordingly the KDE dir layout versus FHS
layout issue will catch us again and again.

Achim


> 
> -- 
> Alan Chandler
> [EMAIL PROTECTED]
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 
> 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
  -- [EMAIL PROTECTED]