all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Troy Figiel <troy@troyfigiel.com>
Cc: 68147@debbugs.gnu.org
Subject: [bug#68147] Naming collision
Date: Sat, 30 Dec 2023 18:21:55 +0100	[thread overview]
Message-ID: <ZZBRs_VQ0rndRiq_@ws> (raw)
In-Reply-To: <87v88fu4jy.fsf@troyfigiel.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

On 2023-12-30 15:51:29 +0100, Troy Figiel wrote:
> Interestingly, both `python-snappy' and `snappy' are available on PyPI
> (https://pypi.org/project/snappy/). These are two completely distinct
> packages and in this issue I only package `python-snappy'.
>
> If I understand the Python naming rules, if someone were to package
> `snappy' in the future, both would be associated to the `python-snappy'
> variable in Guix. What would be the best approach to handle this
> potential naming collision?

As far as I can tell, names of PyPI packages in guix are basically formed by
adding `python-' prefix to the PyPI name.  So here the correct name would be
`python-python-snappy'.  I agree that it looks... weird, however it does prevent
the collision.

It will prevent any user confusion, while adhering to a pattern that is already
elsewhere, so I think it is worth it.

Have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-30 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 13:46 [bug#68147] [PATCH] gnu: Add python-snappy Troy Figiel
2023-12-30 14:51 ` [bug#68147] Naming collision Troy Figiel
2023-12-30 17:21   ` Tomas Volf [this message]
2024-01-06 15:38     ` Troy Figiel
2024-01-06 17:21 ` [bug#68147] [PATCH v2] gnu: Add python-python-snappy Troy Figiel
2024-01-09  8:55   ` bug#68147: " Mathieu Othacehe

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=ZZBRs_VQ0rndRiq_@ws \
    --to=~@wolfsden.cz \
    --cc=68147@debbugs.gnu.org \
    --cc=troy@troyfigiel.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.
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.