From: Milan Zamazal <pdm@zamazal.org>
To: Yngve Svendsen <yngve.svendsen@clustra.com>
Cc: gnats-devel@sources.redhat.com
Subject: Re: Need "usertool" target for make
Date: Sun, 17 Jun 2001 12:26:00 -0000 [thread overview]
Message-ID: <87hexfwafv.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <5.0.0.25.2.20010613163931.00bcae20@mail.trd.clustra.com>
>>>>> "YS" == Yngve Svendsen <yngve.svendsen@clustra.com> writes:
YS> I am unable to find anything resembling the targets "usertools"
YS> and "install-usertools" outlined above in the current master
YS> Makefile, but I don't think adding this would be a lot of
YS> work. However, I am not sufficiently experienced with makefiles
YS> to do this myself.
YS> An alternative would be to add a --tools-only option to
YS> configure. I don't know what solution would be the best, but we
YS> really need to have a way to install the user tools on client
YS> machines before GNATS 4 can be said to be complete.
There used to be the configure option `--with-full-gnats' but that was
removed. However, gnats/Makefile.in still contains the *-gnats and
*-tools targets serving exactly that purpose. They only don't seem to
be propagated to the top-level Makefile.
BTW, the top-level Makefile looks like a horrible mess. It's three
times larger than the Emacs one and it seems to be more general than
needed, I don't like it. Unless anyone objects, I'll clean it up,
together with moving the documentation to a separate directory.
Milan Zamazal
--
Wasting somebody else's time strikes me as the height of rudeness.
Bill Gates
next prev parent reply other threads:[~2001-06-17 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 7:54 Yngve Svendsen
2001-06-17 12:26 ` Milan Zamazal [this message]
2001-06-17 12:30 ` Yngve Svendsen
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=87hexfwafv.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=gnats-devel@sources.redhat.com \
--cc=yngve.svendsen@clustra.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).