public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Gregory Leblanc <gleblanc@cu-portland.edu>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: ANNOUNCE Support for XML
Date: Mon, 13 Nov 2000 08:54:00 -0000	[thread overview]
Message-ID: <00111316550306.01112@quark.caldera.de> (raw)
Message-ID: <20001113085400.Dja-cNsSDJXEDw4xfg7NTbaiP3Iuw7o1GcZoE4W6vJE@z> (raw)
In-Reply-To: <200011130708.eAD78ur27346@peecee.linuxweasel.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Le Lundi 13 Novembre 2000 07:08, Gregory Leblanc a écrit :
> > In the Makefile, you have the following:
> >       ...
> >       htmldir = $(docdir)/html/docbook-utils-0.6
> >       ...
> >       install-htmlDATA: $(html_DATA)
> >               ...
> >               $(mkinstalldirs) $(DESTDIR)$(htmldir)
> >                                           ^^^^^^^^^^^
> > so the buildrooting is done outside of the "docdir" variable by autoconf
> > default behaviour.
>
> I don't really see how this works, but I'm not an auto* expert (yet).

Assume it is braindead. Did it? Okay, you did half of the way... ;-)

> > I know this is not logical, but I'm not responsible for that.
>
> Do you mean to say that I can't blame my autoconf problems on you?  :)

You haven't autoconf problems. Everyone has a problem with autoconf.

;-)

> > I encourage you to give a try at building once agin the package to check
> > what I'm saying.
>
> I know that this can be fixed somehow, as there are countless other
> packages that work.

It hasn't to be fixed, because it is not a problem. The only problem is that 
when you read the specfile it looks strange that mandir and docdir behave 
differently.

>  In it's current form, I am NOT able to build an
> RPM for the docbook-utils package unless I'm logged in as root.

???? What happens? Should not be needed.

>  The
> RPM guru's say that the only packages that you MUST be root to build are
> the kernel packages, because root access is required to create the DEV
> entries.  If you want info on building RPMs as non-root, let me know as
> I've got a short article on that. I'll post a message to the RPM-list
> tomorrow to see if they can help out.  Thanks,    Greg

No it should not be necessary. First tell me what's wrong with docbook-utils.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

  parent reply	other threads:[~2000-11-13  8:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.9911020827260.19428-100000@gatekeeper.zwax.mtg.c>
1999-11-02  0:45 ` Index creation Christophe Guillon
2000-12-27  6:36   ` ANNOUNCE Support for XML Eric Bischoff
2000-11-09 15:39     ` Eric Bischoff
2000-12-27  6:36     ` Gregory Leblanc
2000-11-10 11:34       ` Gregory Leblanc
2000-12-27  6:36     ` Eric Bischoff
2000-11-12  2:44       ` Eric Bischoff
2000-12-27  6:36     ` Eric Bischoff
2000-11-12  3:49       ` Eric Bischoff
2000-12-27  6:36       ` Gregory Leblanc
2000-11-12 23:09         ` Gregory Leblanc
2000-12-27  6:36         ` Eric Bischoff [this message]
2000-11-13  8:54           ` Eric Bischoff
2000-12-27  6:36 Gregory Leblanc
2000-11-27 11:29 ` Gregory Leblanc
2001-12-19 22:49 ` Eric Bischoff
2001-10-26 14:59   ` Eric Bischoff
2001-12-15  2:50   ` Eric Bischoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00111316550306.01112@quark.caldera.de \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=gleblanc@cu-portland.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).