[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fetching or installing package dev source from VCS: names
From: |
Philip Kaludercic |
Subject: |
Re: Fetching or installing package dev source from VCS: names |
Date: |
Sun, 16 Oct 2022 08:31:53 +0000 |
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> Given what this command does, according to the documentation just
> posted, I suggest we call it
>
> package-dev-source
>
> or
>
> package-upstream-source
>
> to correspond clearly to what it does.
Which command specifically? `package-vc-install' or some other command?
> Corresponding index entries could be these two.
>
> @cindex package development source
> @cindex package upstream source
>
> Whether it is good to include them depends on what the
> sorted index will look like with them and without them.
> One or both might be redundant, or miht not.
OK, I will try that out.
> In the case of NonGNU ELPA, which repo does this access?
> Our repo?
That is open, the repository it uses depends on the metadata that ELPA
provides. If that is missing it uses a heuristic to guess a repository
from the URL, in case contains a link to a "well-known" source force.
As I was planning to work on adding the Metadata to ELPA, I'm curios to
know what you think would be preferable? From the tone of your question
I would guess the ELPA mirror, right? If so, I'd be interested what
difference it would make.
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, (continued)
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Lars Ingebrigtsen, 2022/10/08
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Philip Kaludercic, 2022/10/08
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Lars Ingebrigtsen, 2022/10/09
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Philip Kaludercic, 2022/10/09
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Lars Ingebrigtsen, 2022/10/09
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Philip Kaludercic, 2022/10/09
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Lars Ingebrigtsen, 2022/10/10
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Philip Kaludercic, 2022/10/10
- Re: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS, Philip Kaludercic, 2022/10/13
- Fetching or installing package dev source from VCS: names, Richard Stallman, 2022/10/15
- Re: Fetching or installing package dev source from VCS: names,
Philip Kaludercic <=
- Re: Fetching or installing package dev source from VCS: names, Richard Stallman, 2022/10/18
- Re: Fetching or installing package dev source from VCS: names, Philip Kaludercic, 2022/10/19
- Re: Fetching or installing package dev source from VCS: names, Stefan Monnier, 2022/10/19
- Re: Fetching or installing package dev source from VCS: names, Richard Stallman, 2022/10/21
- package-contact-maintainer, Richard Stallman, 2022/10/15
- Re: package-contact-maintainer, Philip Kaludercic, 2022/10/16
- Re: package-contact-maintainer, Stefan Kangas, 2022/10/16
- Re: package-contact-maintainer, Philip Kaludercic, 2022/10/16
- Fetching or installing package dev source from VCS: manual style, Richard Stallman, 2022/10/15
- Re: Fetching or installing package dev source from VCS: manual style, Philip Kaludercic, 2022/10/16