all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Lynn Winebarger <owinebar@gmail.com>,
	 Yuan Fu <casouri@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Unboxed package manager
Date: Tue, 21 Mar 2023 19:10:25 +0000	[thread overview]
Message-ID: <87a605or8e.fsf@posteo.net> (raw)
In-Reply-To: <87sfdxgc0f.fsf@gmail.com> (Augusto Stoffel's message of "Tue, 21 Mar 2023 20:06:24 +0100")

Augusto Stoffel <arstoffel@gmail.com> writes:

> On Mon, 20 Mar 2023 at 15:25, Philip Kaludercic wrote:
>
>> I just skimmed through the initial message, and when reading this my
>> initial thought is does the the advantage justify effort/complexity,
>> considering that most users have an order of magnitude fewer packages
>> installed (of which a few are installed using package-vc which IIUC
>> would explicitly not want to make use of this feature).
>
> I do think there's at least one aspect of this idea that many many
> people need, namely: a simple way to add a directory such as
> ~/.emacs.d/lisp to the load path, with automatic support for autoloads,
> byte-compilation and what not.  Such a thing is also useful if you are
> developing some package, say at ~/project/mypackage.
>
> A package manager exploiting this form or organizing elisp libraries
> would be nice for some, I guess, but certainly it's a more niche
> necessity.

There is no strict need for this to be a package manager.  I propose
something like that a year ago:

  https://wwwcip.cs.fau.de/~oj14ozun/src+etc/site-lisp.el

In principle I could bundle this into a package and add it to ELPA.

-- 
Philip Kaludercic



  reply	other threads:[~2023-03-21 19:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  1:18 Unboxed package manager Lynn Winebarger
2023-03-20  6:30 ` Yuan Fu
2023-03-20  8:55   ` Lynn Winebarger
2023-03-20  9:09     ` Lynn Winebarger
2023-03-20 15:25       ` Philip Kaludercic
2023-03-20 16:12         ` Lynn Winebarger
2023-03-20 16:53           ` Philip Kaludercic
2023-03-20 18:11           ` Jonas Bernoulli
2023-03-21  1:40             ` Lynn Winebarger
2023-03-22 11:17               ` Jonas Bernoulli
2023-03-22 14:31                 ` Lynn Winebarger
2023-03-22 23:39                   ` Lynn Winebarger
2023-03-21 19:06         ` Augusto Stoffel
2023-03-21 19:10           ` Philip Kaludercic [this message]
2023-03-21 19:57             ` Augusto Stoffel
2023-03-21 20:06               ` Philip Kaludercic
2023-03-21  0:23       ` Gregory Heytings
2023-03-21  0:25         ` Gregory Heytings
2023-03-21  1:55           ` Lynn Winebarger
2023-03-21 10:36             ` Lynn Winebarger
2023-03-21 10:52               ` Gregory Heytings
2023-03-21 13:23                 ` Eli Zaretskii
2023-03-21 13:33                   ` Gregory Heytings
2023-03-21 14:13                     ` Eli Zaretskii
2023-03-21 14:20                       ` Gregory Heytings
2023-03-21 17:29                         ` Eli Zaretskii
2023-03-22  0:48                           ` Lynn Winebarger
2023-03-22 14:42                             ` Eli Zaretskii
2023-03-22 22:22                               ` Lynn Winebarger
2023-03-23  6:46                                 ` Eli Zaretskii
2023-03-23 13:30                                   ` Lynn Winebarger
2023-03-24 17:54                                     ` chad
2023-03-26  1:51                                       ` Lynn Winebarger
2023-03-23  1:44                               ` David Masterson
2023-03-23  7:02                                 ` Eli Zaretskii
2023-03-22  7:29                           ` tomas

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=87a605or8e.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=arstoffel@gmail.com \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=owinebar@gmail.com \
    /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.