unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Getting to 1.0!
Date: Tue, 15 Jan 2019 23:34:47 +0100	[thread overview]
Message-ID: <87d0oxwnw8.fsf@gnu.org> (raw)
In-Reply-To: <87r2dftkxc.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 14 Jan 2019 14:42:39 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

>> FOSDEM is only a couple of weeks away, and as we know, FOSDEM is the
>> proclaimed deadline for 1.0.  We’ve come a long way but there are still
>> quite a few things to address before we can reasonably release 1.0:
>>
>>   https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/1.0.org
>
> I have picked up work on a texlive profile hook and have something
> that’s already working.  I’d like to make a few more changes before
> asking for a review, though, as the current version does not work with
> “texlive-tiny”, making it a little too difficult to use as *all*
> packages (including the LaTeX base packages) need to be specified
> manually.
>
> I’m confident that we’ll have something ready in time for 1.0.

… and you completed it a day later, woohoo!  \o/

I wonder if we should add section in the manual about ‘texlive’
packages?  The main difficulty is finding which package provides what
one is looking for, so perhaps a little guidance would be welcome, at
least for the most common packages.

Thoughts?

Ludo’.

  parent reply	other threads:[~2019-01-15 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 22:12 Getting to 1.0! Ludovic Courtès
2019-01-14 13:42 ` Ricardo Wurmus
2019-01-14 14:39   ` Pierre Neidhardt
2019-01-15 22:34   ` Ludovic Courtès [this message]
2019-01-15 22:47     ` Pierre Neidhardt

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=87d0oxwnw8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).