From: Andreas Davour <ante@update.uu.se>
Cc: kai.grossjohann@gmx.net
Subject: Re: Development package hint in INSTALL for GNU/Linux?
Date: Thu, 1 May 2003 13:29:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0305011324510.5984-100000@Tempo.Update.UU.SE> (raw)
In-Reply-To: <E19AkO2-0008JQ-00@fencepost.gnu.org>
On Wed, 30 Apr 2003, Richard Stallman wrote:
> Maybe it's best to just note that the header files are needed. If we start
> mentioning Debian/RedHat package names they'll probably change names next
> week.
>
> Don't worry about that. We can say that these were the names as of
> such and such a month. It is better to give names that may have changed
> than not give them at all.
Ok, with such a date mentioned it feels a lot more fair. Obsolete
information can create more problem that it helps, but that way it at
least has a time frame when it's correct.
> Or is it more than the header files that are needed?
>
> It is not just headers. Often the linkable versions of the shared
> libraries are in separate packages.
Ok. Then packages might a better idea than mentioning specific
files. Even though one or two components might fall in between anyway.
/andreas
=================== Emacs =====================
mail: ante@update.uu.se
or try: Koraq@yahoo.com
groove out at: http://www.update.uu.se/~ante/
====== The choice of a GNU generation! ========
next prev parent reply other threads:[~2003-05-01 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 5:12 Development package hint in INSTALL for GNU/Linux? Kai Großjohann
2003-04-28 8:37 ` Stephen J. Turnbull
2003-04-29 5:39 ` Richard Stallman
2003-04-29 7:06 ` Andreas Davour
2003-04-29 12:02 ` Robert J. Chassell
2003-04-30 5:44 ` Richard Stallman
2003-05-01 11:29 ` Andreas Davour [this message]
2003-04-30 7:59 ` Kai Großjohann
2003-04-30 9:55 ` Glenn Morris
2003-04-30 12:33 ` Kai Großjohann
2003-05-01 3:19 ` Richard Stallman
2003-05-01 11:46 ` Andreas Davour
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0305011324510.5984-100000@Tempo.Update.UU.SE \
--to=ante@update.uu.se \
--cc=kai.grossjohann@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).