Re: Fetching or installing package dev source from VCS: manual style

[Philip Kaludercic]

Rudolf Adamkovič <salutis@me.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> How about "hack on the package sources and add new features to share
>> with others"?
>
> Honestly?  The term "new features" has become the central mantra of all
> modern "agile" software (read: "shit").  With free software, we can have
> a more mature approach.
>
> One might want to hack on a package to learn from it.  Or to discuss it
> with a friend.  Or to add some tests.  Or simply to have fun!
>
> (If I had to pick two verbs for the sentence, I would go with "hack" and
> "share".  No "new features" needed.)

I have no strong opinions on the specific phrasing, as I am not
convinced that "new features" is anything more than a descriptive term.
But if you prefer it, we can change it to "hack on packages and share
your changes with others".

>> Hmm, I see what you mean but I don't know if this is a good idea in
>> general when using `package-update-all' to have a log buffer pop up
>> for every package.
>
> I imagine a list of packages, similar to 'list-packages', e.g.
>
> | Package       | Current |   New | Details          | Description 
> |---------------+---------+-------+------------------|------------------
> | [[ vertico ]] |    0.27 |  0.28 | [[ 17 changes ]] | VERTical Inte...
> | [[ magit   ]] |   3.2.1 | 3.3.0 | [[ 80 changes ]] | A Git porcela...
>
> where [[ ... ]] denotes a button.
>
> A single click on the "17 changes" button would then open the version
> control log with the 17 commits between Vertico 0.27 and 0.28, Emacs
> experience!

I am uncertain if vc would allow for such a thing to be inspected right
now.  I'd like to be able to get package-vc into a functional state
before Emacs 29 is cut off, so I would consider this at a later point.

> Rudy