From: Kaloian Doganov <kaloian@doganov.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: gnewsense-users@nongnu.org, Yavor Doganov <yavor@gnu.org>,
Romain Francoise <romain@orebokech.com>,
gns-devel@ivanovi.net, emacs-devel@gnu.org
Subject: Re: Emacs 22.1 Debian packages
Date: Thu, 07 Jun 2007 08:02:15 +0300 [thread overview]
Message-ID: <87ps48jr1k.fsf@doganov.org> (raw)
In-Reply-To: <871wgoyfo1.fsf_-_@stupidchicken.com> (Chong Yidong's message of "Wed\, 06 Jun 2007 16\:46\:38 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
There is currently no Debian package for Emacs 22.1 usable on the
stable distribution (etch) or oldstable distribution (sarge) of
Debian
If we get this working, we could put the debs on Romain's site and
link to them from the Emacs homepage. Alternatively, we can put
the debs on ftp.gnu.org. I know we don't usually offer binaries,
but I'd argue that it is justifiable in this case. Many free
software packages offer binaries in the form of .rpms and .debs,
and I don't think there's any reason in principle why we
shouldn't, especially in this case where Romain has already done
most of the heavy lifting.
What do people think?
It makes much more sense to target gNewSense, not Debian. GNU Emacs
22.1 is already packaged for gNewSense by Yavor Doganov:
http://chushkopek.org/jungle/
His packaging work is based on Romain's emacs-snapshot, I think.
--
"Every non-free program has a lord, a master --
and if you use the program, he is your master." --RMS
next prev parent reply other threads:[~2007-06-07 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ps49t08e.fsf@stupidchicken.com>
[not found] ` <87tztk3kyv.fsf@elegiac.orebokech.com>
2007-06-06 20:46 ` Emacs 22.1 Debian packages Chong Yidong
2007-06-06 21:46 ` David Diaz
2007-06-07 5:02 ` Kaloian Doganov [this message]
2007-06-08 7:11 ` Richard Stallman
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=87ps48jr1k.fsf@doganov.org \
--to=kaloian@doganov.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=gnewsense-users@nongnu.org \
--cc=gns-devel@ivanovi.net \
--cc=romain@orebokech.com \
--cc=yavor@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.