This is the mail archive of the
mailing list for the Cygwin project.
RE: [ANNOUNCEMENT] GNU emacs 21.2-7 packages available
- From: "Harig, Mark A." <maharig at idirect dot net>
- To: "Joe Buehler" <jbuehler at hekimian dot com>,<cygwin at cygwin dot com>
- Date: Tue, 3 Sep 2002 15:38:01 -0400
- Subject: RE: [ANNOUNCEMENT] GNU emacs 21.2-7 packages available
OK. I agree that it's best to follow the documented behavior.
'awk'/'gawk' follows that rule also, i.e., puts its binaries
into /usr/sbin/awk/. All other packages use either /usr/lib
or /usr/libexec, e.g., cvs, groff, mingw, perl, python,
squid. Maybe one of the Cygwin developers needs to weigh
in on what the rule should be, i.e., where should "internal"
programs/libraries be put, and if it is different from FHS,
then why is it different?
> -----Original Message-----
> From: Joe Buehler [mailto:email@example.com]
> Sent: Tuesday, September 03, 2002 1:08 PM
> To: firstname.lastname@example.org
> Subject: Re: [ANNOUNCEMENT] GNU emacs 21.2-7 packages available
> Harig, Mark A. wrote:
> > Based upon the Filesystem Hierarchy Standard (FHS) at
> > http://www.pathname.com/fhs/, it would appear that the
> > more appropriate place for these files is
> > /usr/libexec/emacs/21.2/i686-pc-cygwin/. (Alternatively,
> > these files could be placed in
> > /usr/lib/emacs/21.2/i686-pc-cygwin/.)
> The following is from the Cygwin page dealing with
> contributed packages.
> That's why emacs is where it is at present.
> Joe Buehler
> * The package is configured using (at a minimum) the
> following paths:
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html