search

progfolio / elpaca

An elisp package manager
GNU General Public License v3.0
572 stars 27 forks source link

[Bug/Support]: Origin of packages installed #328

Open bmp opened 3 days ago

bmp commented 3 days ago

Confirmation

Elpaca Version

Elpaca b8ed514 HEAD -> master, origin/master, origin/HEAD installer: 0.7 emacs-version: GNU Emacs 31.0.50 (build 5, x86_64-pc-linux-gnu, GTK+ Version 3.24.42, cairo version 1.18.0) of 2024-07-03 git --version: git version 2.45.2

Operating System

OS: Fedora Linux 40 (KDE Plasma) x86_64 Kernel: Linux 6.9.7-200.fc40.x86_64

Description

I checked the wiki and the issues, but maybe my search terms were wrong. But here is a very short description of what I have noticed. I'm not sure if it is a bug or if it is my configuration, so I haven't edited the title.

I use packages from the respective repositories, MELPA and ELPA. However, in the elpaca manager buffer, many show up as MELPA/ELPA even though I am setting them up as from the source repositories, I have attached screenshots below for two packages which I am fetching from the repostories, there are more such examples in my setup. Is it because of some configuration that I have or is this expected behaviour? Though the full recipe is correct, shouldn't the source also be based on the full recipe rather than menu item recipe?

  1. Wallabag: Showing source as init file: Screenshot_20240703_184814 The recipe being used: Screenshot_20240703_184828

  2. Mastadon: Showing the source as MELPA: Screenshot_20240703_185127 The recipe being used: Screenshot_20240703_185138

progfolio commented 3 days ago
  1. Wallabag: Showing source as init file:

A Wallabag menu item does not exist in any of the pre-configured ELPAs, so the source is set to "Init File" for convenience's sake.

  1. Mastadon: Showing the source as MELPA:

Altering the recipe in your init file does not change the menu item's source. To give a real world analogue, ordering a burger from McDonald's with extra pickles doesn't make the recipe "homemade".

The elpaca-info view shows the original menu-item recipe. It also shows the computed recipe (the result of any configuration/modifications plus the inherited properties from that particular menu item) that would be used with that source.

In the manager view you can use the #installed #unique search tags to show packages which are installed and which sources they are pulling any recipe inheritance from. Is there something in particular you'd hope to gain from seeing the source be "Init File" (which is implied by virtue of them being installed) for those packages? If I have a clearer picture of what you're trying to achieve, I may be able to suggest a custom search tag which shows what you'd like.

bmp commented 16 hours ago

The analogue does make it clear, thank you!

Here is what I was hoping to achieve:

  1. There are a number of packages that I use from the repositories directly even though they are on MELPA, ELPA, etc. I do this because I sometimes need a different branch than the ones on these sources.
  2. I was hoping to quickly filter these packages that are fetched from such sources, and then be able to see the changes made to these packages at source before I merge them.

Does this make sense?