unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: rustom <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: An alternative to a monolithic ~/.emacs init file
Date: Wed, 14 Nov 2007 03:52:43 -0000	[thread overview]
Message-ID: <1195012363.196769.13490@z24g2000prh.googlegroups.com> (raw)
In-Reply-To: <87wssm4htk.fsf@lion.rapttech.com.au>

Thanks Tim for the pointers.



On Nov 13, 2:26 pm, Tim X <t...@nospam.dev.null> wrote:
> Ah, yep, your running into one of the issues with using a distro packaging
> system. Packages like ecb depend on a stand alone speedbar package (as do
> the others you listed, but don't know about speedbar now being packaged in
> emacs itself. I'm not sure if you could use the force option to apt to
> install ecb or not. The other issue may also be that I think the bundled
> speedbar version in emacs 22 is older than the version in the stand alone
> package (at least, this was the case some time back before emacs 22 was
> released.)

This is clearly a bigger problem than people are accepting: viz that
there are large systems of packages which are tolerably consistent in
themselves but dont talk nice to each other -- think of
apt <-> emacs
apt <-> ruby/python
eclipse <-> python
apt <-> webmin

I believe that a decent response to this issue will need:
1. A carefully thought-out standardized data oriented way (not XML
please!) for managing package repos
2. An event driven engine maybe along the lines of upstart see
https://wiki.ubuntu.com/ReplacementInit
3. built on an SOA backbone.  Yeah I know that programmers are likely
to think of this as unsubstantiated hype but when we do apt-get
install foo we are using an SOA

  reply	other threads:[~2007-11-14  3:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2759.1193756709.18990.help-gnu-emacs@gnu.org>
2007-11-07 17:13 ` An alternative to a monolithic ~/.emacs init file rustom
2007-11-08 13:08   ` Sebastian Tennant
     [not found]   ` <mailman.3126.1194527313.18990.help-gnu-emacs@gnu.org>
2007-11-08 19:53     ` rustom
2007-11-09 14:18       ` Sebastian Tennant
     [not found]       ` <mailman.3180.1194617919.18990.help-gnu-emacs@gnu.org>
2007-11-10 12:18         ` rustom
2007-11-10 17:13           ` Tom Tromey
     [not found]           ` <mailman.3247.1194750639.18990.help-gnu-emacs@gnu.org>
2007-11-11 15:29             ` rustom
2007-11-12 21:56               ` Tim X
2007-11-13  4:21                 ` rustom
2007-11-13  9:26                   ` Tim X
2007-11-14  3:52                     ` rustom [this message]
2007-11-13  1:22             ` rustom
2007-11-11  0:09       ` Francisco Miguel Colaço
2007-10-30 15:04 Sebastian Tennant
2007-10-30 20:30 ` Sebastian Tennant

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=1195012363.196769.13490@z24g2000prh.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).