all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add slurm-llnl.
Date: Thu, 11 Feb 2016 11:08:01 +0100	[thread overview]
Message-ID: <20160211100801.GA6109@debian.eduroam.u-bordeaux.fr> (raw)
In-Reply-To: <20160211081534.GA8987@thebird.nl>

On Thu, Feb 11, 2016 at 09:15:34AM +0100, Pjotr Prins wrote:
> I am under the impression one should fix one package at a time. What
> is the policy anyway? With or without namespace? Without the namespace
> there is a naming conflict between the openssl license and the openssl
> package (in tls).

We normally use the namespace as soon as there is a collision; and then I
think it is okay to treat the complete file at once. If you want to be
overcorrect, you could first make the namespace change in one commit and
then add your package in a second one.

> > I think we should rather use "slurm-wlm" if we are trying to
> > dissambiguate with the "Slurm the Realtime network interface monitor".
> The website https://computing.llnl.gov/linux/slurm/ suggests
> otherwise. Also archlinux took this name
> https://aur.archlinux.org/packages/slurm-llnl/

And Debian, but we are free to use our own conventions. Do you think it
is likely that we will package the other slurm? Otherwise, I would simply
go with "slurm" now according to our package guidelines; and then we can
still name the other slurm as slurm-nlm or similar.

Andreas

  reply	other threads:[~2016-02-11 10:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 17:36 [PATCH] gnu: Add slurm-llnl Pjotr Prins
2016-02-11  4:04 ` Eric Bavier
2016-02-11  8:15   ` Pjotr Prins
2016-02-11 10:08     ` Andreas Enge [this message]
2016-02-11 11:11       ` Pjotr Prins
2016-02-11 14:21         ` Andreas Enge
2016-02-11 15:00           ` Pjotr Prins
2016-02-12 12:30             ` Pjotr Prins
2016-02-11 15:19         ` Eric Bavier
2016-02-12 12:20     ` Pjotr Prins
2016-02-12 12:30       ` Andreas Enge
2016-02-12 12:31         ` Pjotr Prins
2016-02-12 12:57           ` [PATCH] gnu: Add slurm-wlm Pjotr Prins
2016-02-12 17:51             ` Andreas Enge
2016-02-13  8:59             ` [PATCH] gnu: Add slurm Pjotr Prins
2016-02-13 10:28               ` Andreas Enge
2016-02-13 16:42                 ` Pjotr Prins
2016-02-13 17:00                   ` Andreas Enge
2016-02-13 17:01                   ` Pjotr Prins
2016-02-13 17:20                     ` Andreas Enge
2016-02-13 20:13                       ` Leo Famulari
2016-02-13 20:34                         ` Andreas Enge
2016-02-13 20:40                           ` Leo Famulari
2016-02-14 14:22                             ` Andreas Enge
2016-02-14 19:08                               ` Leo Famulari
2016-02-15 12:09                                 ` Pjotr Prins
2016-02-15 21:51                                   ` Andreas Enge
2016-02-16  7:21                                     ` Pjotr Prins
2016-02-16  9:55                                       ` Andreas Enge
2016-02-13 20:38                         ` Leo Famulari
2016-02-13 21:32                           ` Pjotr Prins
2016-02-13 21:43                             ` Leo Famulari
2016-02-13 17:13                 ` Pjotr Prins
2016-02-11  4:33 ` [PATCH] gnu: Add slurm-llnl Eric Bavier
2016-02-11  8:17   ` Pjotr Prins
2016-02-11  8:28     ` Ricardo Wurmus
2016-02-11 18:36 ` Efraim Flashner

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

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

  git send-email \
    --in-reply-to=20160211100801.GA6109@debian.eduroam.u-bordeaux.fr \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.