[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#66270] [PATCH v2] gnu: mpd-mpc: Install bash completions in correct
From: |
Liliana Marie Prikler |
Subject: |
[bug#66270] [PATCH v2] gnu: mpd-mpc: Install bash completions in correct location. |
Date: |
Fri, 06 Oct 2023 10:59:27 +0200 |
User-agent: |
Evolution 3.46.4 |
Am Donnerstag, dem 05.10.2023 um 17:06 +0200 schrieb Simon Tournier:
> Hi,
>
> On Wed, 04 Oct 2023 at 20:51, Liliana Marie Prikler
> <liliana.prikler@gmail.com> wrote:
>
> > It's not installing it, though – merely moving it from one place in
> > output, to another (the one that's actually consulted by bash).
> > Hence, move.
>
> That’s the definition of “installing files”, no? :-)
>
> --8<---------------cut here---------------start------------->8---
> INSTALL(1) User Commands INSTALL(1)
>
> NAME
> install - copy files and set attributes
>
> DESCRIPTION
> This install program copies files (often just compiled) into
> destination locations you choose.
> --8<---------------cut here---------------end--------------->8---
>
> Anyway. I had my coffee now, so no more bikeshed between “copy” vs
> “move”, which is in this context the same. ;-)
On a high level, copying means that (a copy of) the file persists in
its previous location, whereas move means it does not. The 'move-
convention is used for files that are placed by the build system in
some output location, that we actually want to have in a different
output location.
Cheers