"un-git" the releases deployed from git repos

[Fabien-Chouteau]

What I mean here is to not have releases deployed from git as valid git checkouts.

This idea starts with a discussion with a user that was confused by Alire's behavior. This person wanted to use alr get as a way to checkout a repository to work on it, and was surprised by the fact that alire.toml was modified (see why here: #1385 (comment)).

For me the disconnect is in the expectation that alr get gives when the source of the release is a git repo. Indeed you get a git checkout, but it's a release not a development branch.

What I want to suggest here is to change this behavior and not have releases as valid git checkout. The only way I found to do this is to remove the .git folder after git clone .

[mgrojo]

If you're definitely implementing this, I suggest running git clone with the argument --depth 1, otherwise the clone will download all the history, only to be deleted later, wasting time and bandwidth.

[Fabien-Chouteau]

If you're definitely implementing this, I suggest running git clone with the argument --depth 1, otherwise the clone will download all the history, only to be deleted later, wasting time and bandwidth.

Indeed, in fact we can probably start by doing --depth 1 already.

[rocher]

Also, please consider a "git restore alire.toml" after a fresh clone to avoid seeing this file as modified.

…

On Mon, Sep 18, 2023, 12:15 PM Fabien Chouteau ***@***.***> wrote: If you're definitely implementing this, I suggest running git clone with the argument --depth 1, otherwise the clone will download all the history, only to be deleted later, wasting time and bandwidth. Indeed, in fact we can probably start by doing --depth 1 already. — Reply to this email directly, view it on GitHub <#1455 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPBLD55QORYVQCIMDPTV2LX3ANLZANCNFSM6AAAAAA4Z3JHMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Fabien-Chouteau]

Also, please consider a "git restore alire.toml" after a fresh clone to avoid seeing this file as modified.

The file is modified for a good reason. see here: #1385 (comment)

[rocher]

Thanks Fabien for this reference, good point. Is there a (more complete) explanation of why and how manifests are modified? BR, -- Francesc Rocher

…

On Wed, Sep 20, 2023 at 10:01 AM Fabien Chouteau ***@***.***> wrote: Also, please consider a "git restore alire.toml" after a fresh clone to avoid seeing this file as modified. The file is modified for a good reason. see here: #1385 (comment) <#1385 (comment)> — Reply to this email directly, view it on GitHub <#1455 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPBLD3RUXXQZCMAHMUED3TX3KPFHANCNFSM6AAAAAA4Z3JHMA> . You are receiving this because you commented.Message ID: ***@***.***>