unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Jeremiah@pdp10.guru
Cc: guix-devel@gnu.org
Subject: Re: Cleaning up make clean's behavior
Date: Sat, 2 Jun 2018 16:46:24 +0000	[thread overview]
Message-ID: <20180602164624.zagmwhw5oilreumm@abyayala> (raw)
In-Reply-To: <87a7sd17jz.fsf@ITSx01.pdp10.guru>

Hi Jeremiah,

Jeremiah@pdp10.guru transcribed 946 bytes:
> As running make clean breaks the bootstrap script.
> I propose we leverage git's shallow clones (git clone --depth 1 $URL)
> and include the .git directory with the repo such that we could simply
> have make clean check for git and if it exists run git clean -xdf and
> then only if git fails to exist, fallback to the existing broken form;
> which needs to be corrected.
> 
> per discussion with g_bor[m] about the default automake clean rules
> being used currently; and per their suggestion bringing this question to
> this distribution list for further discussion.

Where did this discussion take place? Would be good to read some
details if possible.

ng0

> Additional wouldn't one want to pack the .git in the tarball to enable a
> simplified update method.
> 
> jlicht pointed out that this would not be a problem yet for guix, but it
>  does seem unconventional. It would not make sense for some bigger-repo projects (e.g. emacs) for sure though
> 
> Given that discussion background does anyone have any problems, concerns
> or issues with the change proposed?
> 

  reply	other threads:[~2018-06-02 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02 16:23 Cleaning up make clean's behavior Jeremiah
2018-06-02 16:46 ` Nils Gillmann [this message]
2018-06-02 16:54   ` Gábor Boskovits
2018-06-03  0:29 ` Mark H Weaver
2018-06-03  6:29   ` Vincent Legoll
2018-06-04 11:36 ` Ludovic Courtès
2018-06-10  6:41   ` Chris Marusich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180602164624.zagmwhw5oilreumm@abyayala \
    --to=ng0@n0.is \
    --cc=Jeremiah@pdp10.guru \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).