From: Ian Barton <lists@manor-farm.org>
To: emacs-orgmode@gnu.org
Subject: Re: packaging org-mode & worg
Date: Thu, 24 Jun 2010 10:34:42 +0100 [thread overview]
Message-ID: <4C2326B2.2030306@manor-farm.org> (raw)
In-Reply-To: <83mxumuguf.fsf@yahoo.it>
> Some question come to my mind (see below for a general question):
>
> Could you, please, elaborate who are the distribution editors?
>
> + Carsten with file org-mode.zip?
> + FSF emacs+[stable]-orgmode?
>
> and what do mean, when you say "upstream"/"downstream" packages?
>
Disclaimer I am not Stefano:) It's fairly common for Linux distros to
split large applications into smaller packages. A good example would be
MythTV, which Debian split into a number of packages that support
different features.
This used to be the case for Emacs, but since Emacs 23 most things seem
to be included in the core version.
To use the Debian analogy the upstream would be Carsten and downstream
would be whoever created the Debian packages. The packagers commonly
feed back bug reports/bug fixes to the upstream, plus suggestions on how
to make the code easier to build packages.
One possible solution to the "Worg Problem" would be to create a ppa
(Personal Package Archive) on Launchpad. This would create a debian
package of Worg, which would at least help Debian/Ubuntu users. The
reason I suggest Launchpad is that it has a number of automated build
facilities that reduce the work the package maintainer has to do to keep
the package up to date.
Ian.
next prev parent reply other threads:[~2010-06-24 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 11:30 packaging org-mode & worg Giovanni Ridolfi
2010-06-24 9:34 ` Ian Barton [this message]
2010-06-25 9:36 ` Stefano Zacchiroli
2010-06-25 23:16 ` Bastien
2010-06-26 14:24 ` Ian Barton
2010-06-26 14:31 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C2326B2.2030306@manor-farm.org \
--to=lists@manor-farm.org \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).