From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: prompt to create non existent directory.
Date: Thu, 02 Nov 2017 15:25:18 +0100 [thread overview]
Message-ID: <864lqcwyep.fsf@zoho.com> (raw)
In-Reply-To: 20171102131915.GA6089@tuxteam.de
t wrote:
> Because for ~98% of those packages I want
> "tried and tested" and not "latest and
> greatest". The other 2% I care specially for
> I put more admin work into (and bear with
> ocassional breakage).
>
> [...]
>
> It's still one gadget per app to take care
> of. I don't feel like feeding thousands of
> gadgets, even if they are shell scripts.
The issue with the "~2%" is that the repo's SW
is too old or sometimes unavailable.
Why can't this be available without doing it
100% manually? Well, it can, and that's what
those gadgets do! Why not for Emacs as well?
We have [M]ELPAs for additional software.
Why is it such a far-fetched idea upgrading
Emacs in a similar manner, if it can be done,
as I suspect it can?
If you for development or other reasons want to
get the source and compile it nobody is
stopping you!
The ideal situation is: the distro's pack
manager gets you whatever piece of SW you want,
in any state you want, at whatever version.
All thru the same interface.
OK, so this isn't the case. What's wrong with
bridging the gap by those specialized getters
and upgraders? Which are also shell tools with
a similar, tho not identical, interface.
But similar in terms of the UX.
You say you want the distro's pack manager for
98% and compile for 2%. Why not the distro for
94.5%, the gadgets for 4%, and compilation for
1.5%? Or any other distributions anyone
would want?
I fail to see how this is a principal question!
It is just a matter of convenience. Some people
aren't happy with what they find in the repos.
So the do their own managers because people
generally find that easier and less work than
getting the source and compiling manually.
Isn't that the reason for the pack managers to
begin with? If it is a good idea once, why not
twice or how many times people see the
need for?
The repos are good but not perfect or
universal. Specialized needs find specialized
solutions. Perhaps one day that will enter the
repos to a degree it won't be needed.
Who knows?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-11-02 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 19:36 prompt to create non existent directory Deric Bytes
2017-10-27 19:53 ` Skip Montanaro
2017-10-30 1:43 ` Stefan Monnier
2017-10-27 20:10 ` tomas
2017-10-27 22:52 ` Emanuel Berg
2017-10-28 7:01 ` tomas
2017-11-02 9:44 ` Emanuel Berg
2017-11-02 10:57 ` tomas
2017-11-02 13:03 ` Emanuel Berg
2017-11-02 13:19 ` tomas
2017-11-02 14:25 ` Emanuel Berg [this message]
2017-11-02 14:44 ` tomas
2017-11-02 15:06 ` Emanuel Berg
2017-11-02 15:17 ` tomas
2017-10-28 0:48 ` Nick Helm
2017-10-28 7:20 ` Amos Bird
[not found] ` <mailman.2358.1509135046.27995.help-gnu-emacs@gnu.org>
2017-10-28 19:41 ` Deric Bytes
2017-10-28 19:55 ` Eli Zaretskii
[not found] ` <mailman.2416.1509220530.27995.help-gnu-emacs@gnu.org>
2017-10-28 20:20 ` Deric Bytes
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=864lqcwyep.fsf@zoho.com \
--to=moasen@zoho.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.
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.