From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: send-pr, time to borgify it?
Date: Sun, 24 Apr 2005 00:28:00 -0000 [thread overview]
Message-ID: <20050424001718.GC537@wookimus.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2040 bytes --]
Well, the adventure with automake continues. I'm starting to get a
good feel for things. Reading the automake manual requires you to pay
attention, but most of the information I need is there.
One thing I've come to question is whether or not we care to retain
the separate send-pr directory. It appears that send-pr was intended
to operate with or without the presence of pr-edit and query-pr,
falling back to sendmail. It could be distributed to your
customer/client as a generic shell script with no external
dependencies.
Currently, I've retained and updated the configure.ac file in send-pr,
added Makefile.am and dumped Makefile.in (built by automake). We
*could* distribute send-pr independent of GNATS, but *should* we?
(This isn't rhetorical. I would really like to know your opinions.)
Over the years, it appears that the send-pr.texi manual has been fully
integrated into the GNATS manual. Additionally, the emacs *.el file
has been dropped in favor of the gnats.el file. By all indications,
send-pr doesn't appear to exist separately from GNATS at all. If one
wishes to distribute send-pr to a customer, she could tarball up
send-pr, send-pr.1, install-sid, and install-sid.8. Even that is not
highly necessary. The functionality of install-sid (updating a config
file) could be rolled into send-pr.
Hmm... I just did a search against help-gnats for send-pr to see if
this conversation had popped up in the past and found an interesting
post. [1]_ It appears that Yngve had created a manpage for
send-pr.conf back in 2001 that doesn't appear to exist in our CVS
repository. We should probably roll that in, updated for today's use.
;-)
So, what do you folks say? Roll send-pr into GNATS proper and dump
the extra build infrastructure or keep it pseudo-separate?
.. [1] http://lists.gnu.org/archive/html/help-gnats/2001-05/msg00040.html
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2005-04-24 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 0:28 Chad Walstrom [this message]
2005-04-24 5:10 ` Mark D. Baushke
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=20050424001718.GC537@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
/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).