unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Todor Kondić" <tk.code@protonmail.com>,
	"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Integrating many packages in Guix at once
Date: Sun, 07 Jul 2019 09:32:32 +0200	[thread overview]
Message-ID: <389E3C97-549A-4589-BF00-7D444846E8D8@lepiller.eu> (raw)
In-Reply-To: <YlhqcPEFOvpKrHV1Z3fyjit-gFN1N5fLCxvq-U629xgnAcb97GC58bFR52BdWVR49tjF3532uSGflPaozpOocld-AjdaFdrSpDlA3O1KsMI=@protonmail.com>

Le 7 juillet 2019 09:18:46 GMT+02:00, "Todor Kondić" <tk.code@protonmail.com> a écrit :
>Hi,
>
>Our work at LCSB-ECI
>https://wwwen.uni.lu/lcsb/research/environmental_cheminformatics
>depends on few top-level R packages such as RMassBank, ReSOLUTION and
>RChemMass. These pull in many massspec related dependencies that I
>noticed (last time i checked) are not yet in the official Guix.
>
>What is the best strategy to integrate all those packages and the
>dependencies in Guix? A single commit? A package per commit (this
>sounds like i won't have time for that)? Suggestions are appreciated.
>
>The packages in question are available as a public Guix channel from:
>https://git-r3lab.uni.lu/eci/eci-pkg-menu
>
>Thanks!
>
>Todor

Hi,

We always do one package per commit. Unless I oversaw something, it's only a dozen packages, so it shouldn't be too difficult to copy-paste them in guix' sources, right? Before that, you'll have to make sure the description contains only full sentences. (The easiest way is to start with "R-something is …")

Once you have one commit per package, you can send them all together with git send-email.

Thanks for your work!

      reply	other threads:[~2019-07-07  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07  7:18 Integrating many packages in Guix at once Todor Kondić
2019-07-07  7:32 ` Julien Lepiller [this message]

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=389E3C97-549A-4589-BF00-7D444846E8D8@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=tk.code@protonmail.com \
    /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. 
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).