Gnus development mailing list
 help / color / mirror / Atom feed
* Installation, activation and setup of packages (e.g. Gnus) (was: Integrating package.el)
       [not found]                             ` <87aawsh7ou.fsf@lifelogs.com>
@ 2010-01-05 17:27                               ` Reiner Steib
  0 siblings, 0 replies; only message in thread
From: Reiner Steib @ 2010-01-05 17:27 UTC (permalink / raw)
  To: emacs-devel, ding

On Tue, Jan 05 2010, Ted Zlatanov wrote:

> On Mon, 04 Jan 2010 12:51:06 -0700 Tom Tromey <tromey@redhat.com> wrote: 
> Ted> A better setup process for Gnus would be really nice, though.

ACK

> Ted> The usual pre-install and post-install scripts you find in RPM
> Ted> or DEB would help.

Those don't start per-user setup.  The (missing) setup process (using
Gnus half-done assistant.el or anything else) is per-user: configuring
news server, mail sources, IMAP, SMTP.

> Ted> I suspect many other packages would benefit from a better setup
> Ted> process through package.el.
>
> Tom> If you want to try packaging it, I can explain what you need to do.
> Tom> It is usually quite easy.
>
> I think the pre-install and post-install steps are pretty important.
> Without them, packaging Gnus doesn't do much.  I want the post-install
> to actually set up the user's Gnus configuration.  This has been a very
> common complaint about Gnus.  

I don't think the purpose of package.el is to do or start the user
setup.  The Gnus assistant is supposed to be run when a *user* fires
up Gnus for the first time, which is after the package is already
installed and "activated" (by the *administrator*).  I would oppose to
mix admistrative tasks (installation) with user setup.

> Installing it is the easy part, since it comes with Emacs.  Can
> package.el support that?  I can't tell if this is the "activate" or
> the "load" stage (are they states or state transitions?  English can
> be so ambiguous...) or something new; also it seems like this is
> something external to Gnus, a function of the ELPA wrapper (although
> it may be bundled within Gnus) rather than something Gnus will
> always run for new users.  This is the major question I have before
> I propose this packaging on the Gnus mailing list.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-01-05 17:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <e01d8a50912251855k149637afgc4fbfdafa7ce7cd2@mail.gmail.com>
     [not found] ` <E1NOjZl-000824-Fh@fencepost.gnu.org>
     [not found]   ` <e01d8a50912261924i3776bb22wbf2f2685e2fdc706@mail.gmail.com>
     [not found]     ` <E1NPKdi-00023n-J8@fencepost.gnu.org>
     [not found]       ` <e01d8a50912281055w2801b736te6d05dc2733ae83a@mail.gmail.com>
     [not found]         ` <m3ljgm5wh9.fsf@verona.se>
     [not found]           ` <878wclke6j.fsf@lifelogs.com>
     [not found]             ` <E1NPh5D-0000wW-NG@fencepost.gnu.org>
     [not found]               ` <87k4w5lbyb.fsf_-_@lifelogs.com>
     [not found]                 ` <m3vdfpsbrm.fsf@fleche.redhat.com>
     [not found]                   ` <87zl50jv52.fsf@lifelogs.com>
     [not found]                     ` <m3hbr5k51j.fsf@fleche.redhat.com>
     [not found]                       ` <87d41rn3wt.fsf_-_@hagelb.org>
     [not found]                         ` <87k4vxiwlj.fsf@lifelogs.com>
     [not found]                           ` <m3d41pfy39.fsf@fleche.redhat.com>
     [not found]                             ` <87aawsh7ou.fsf@lifelogs.com>
2010-01-05 17:27                               ` Installation, activation and setup of packages (e.g. Gnus) (was: Integrating package.el) Reiner Steib

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 NNTP newsgroup(s).