From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Federated package management [was Recursion problems with package management]
Date: Fri, 14 Aug 2015 22:31:15 -0700 (PDT) [thread overview]
Message-ID: <69f93287-534f-425e-b4d8-5cfa8f0a0296@googlegroups.com> (raw)
In-Reply-To: <f25da06d-d66b-4db0-88aa-526dc6f7a16a@googlegroups.com>
On Saturday, August 15, 2015 at 8:53:39 AM UTC+5:30, Ian Zimmerman wrote:
> 3. Clearly we don't want maintainers to do separate packaging work for
> each distro. So, this is something that needs to be standardized among
> the distros. They _are_ willing to do that, when there's compelling
> technical case for it.
And what is the fate of emacs users on package-manager-less OSes?
[Yeah snarky comments about Windows are appropriate here.
Except for the fact that well-known distros like slackware would also belong!
]
prev parent reply other threads:[~2015-08-15 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 2:30 Recursion problems with package management Rusi
2015-08-15 3:23 ` Ian Zimmerman
[not found] ` <mailman.8364.1439609016.904.help-gnu-emacs@gnu.org>
2015-08-15 3:45 ` Federated package management [was Recursion problems with package management] Rusi
2015-08-15 5:31 ` Rusi [this message]
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=69f93287-534f-425e-b4d8-5cfa8f0a0296@googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@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).