Ludovic Courtès ezt írta (időpont: 2018. júl. 6., P, 23:05):
> Hello,
>
> Mark H Weaver skribis:
>
> > Why do you say that only upstream needs to worry about it? I would
> > think that you could say the same thing about almost any test suite, but
> > there's always the possibility that our
Hooray :)
Nitpick and complain: Could we please send this to guix-devel as TO and use BCC
for the rest or even: separate emails? I'm getting so many duplicates with every
release. I know it's a timesaver, but cross-posting and then people replying
with
"reply to all" to cross-posted messages can
Is it an idea to also have a current Guix archive on the download
page? Or at least a link to one?
https://www.gnu.org/software/guix/download/
Ever so often I need to rescue a running Guix system which won't run
guix pull and even a build-from-source quickly. Being able to do
guix archive
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> If we feel that very few of our users care about git-svn interop,
>> another option would be to add a lighter variant of 'git' that does not
>> include SVN support. It would probably be a good idea to have a
>>
Mark H Weaver writes:
>>> Also, looking ahead, I think it would be great if we could eventually
>>> move to a model where the tests of some packages are split off into
>>> separate derivations. Similarly, we could work toward splitting off
>>> documentation generation to separate derivation
On Fri, Jul 06, 2018 at 23:05:04 +0200, Ludovic Courtès wrote:
> Instead of ‘git-minimal’, we could have ‘git’ without SVN support, and
> have a separate ‘git-svn’ package. We can probably arrange for that
> ‘git-svn’ package to only provide the relevant libexec/git-core bits
> (git-svn is just a
