Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Clarify naming conventions for packages with periods in their name
Date: Thu, 09 Jul 2020 02:42:15 +0200	[thread overview]
Message-ID: <20200709004215.oXIKydrXF-IJtPlwyoXqPfKStxAzdgBsmyZQobaxy28@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4777@inbox.vuxu.org>

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

Closed issue by yousefamar on void-packages repository

https://github.com/void-linux/void-packages/issues/4777

Description:
I was writing a template (my first) for [this CLI tool](https://github.com/todotxt/todo.txt-cli) that happens to have a period in its name. I've seen this before with programs that e.g. have a ".io" as part of their brand. Are periods kept in the name?

Other package managers rename packages like this to something more normal, and indeed the official brew version of this packages is called "todo-txt" rather than "todo.txt-cli".

There seems to be precedent in `srcpkgs` as some packages have a period in them ([here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/AlsaMixer.app/template) and [here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/R-cran-data.table/template)).

Any pointers (or additions to [this section of the manual](https://github.com/void-linux/void-packages/blob/master/Manual.md#programs)) would be much appreciated!

           reply	other threads:[~2020-07-09  0:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4777@inbox.vuxu.org>]

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=20200709004215.oXIKydrXF-IJtPlwyoXqPfKStxAzdgBsmyZQobaxy28@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).