public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Docbook Tools discussion list
	<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: new tools coming and a couple of renamings
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <3992FCAE.638C81A0@cybercable.tm.fr> (raw)
In-Reply-To: <76zonbe3ji.fsf@odie.lanl.gov>

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

Mark Galassi wrote:
> 
>     Bill> Is it going to be able to compile from source on something
>     Bill> other than RedHat linux or close cousins?
> 
> Indeed it will compile on all sorts of things.  Thanks to Eric's
> cleanup I feel like it's actually worth the effort.
> 
> Our intention is to produce tarballs, and I got your mail as I was
> adding configure.in/Makefile.am files to the docbook-utils package (a
> process known as "autobarfing a package").

Yes, it does compile on a wide range of platforms. It even installs and
works ;-).

What *does not work* is to install the binary RPM on a non-RedHat
cousin.

But if you rebuild the source package on a given platform:

	# rpm -ba SPECS/twiddledoodle.spec

then the generated binary RPM will normally work on that platform. Don't
forget to send the source RPM to the maintainers of this distribution
and to tell them that it worked out - normally they love your doing
their work ;-).

Same for Debian systems, if you repackage the tarball, thanks to Mark's
efforts in the automake/autoconf area.

-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

  reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Mark Galassi
2000-12-27  6:36 ` esr
2000-12-27  6:36   ` Sylvan Ravinet
2000-07-21  0:08     ` Sylvan Ravinet
2000-12-27  6:36   ` Eric Lee Green
2000-12-27  6:36   ` Jorge Godoy
2000-12-27  6:36 ` Norman Walsh
2000-12-27  6:36 ` Bill Brooks
2000-12-27  6:36   ` Mark Galassi
2000-12-27  6:36     ` Eric Bischoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Gregory Leblanc

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=3992FCAE.638C81A0@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    /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).