From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: Daniel Baumann <daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: Re: proper name for userspace package?
Date: Fri, 31 Jul 2009 02:32:34 +0900 (JST) [thread overview]
Message-ID: <20090731.023234.56054455.ryusuke@osrg.net> (raw)
In-Reply-To: <4A71CA72.8080106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
(Cc added to Debian maintainer)
On Thu, 30 Jul 2009 11:29:38 -0500, Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> I'm wondering what the preferred name is for the userspace package.
>
> The tarball is "nilfs-utils" but debian has "nilfs2-tools" - is there a
> preference, or is this a debian convention that caused the rename?
>
> Thanks,
> -Eric
I don't know the how and why. The btrfs was also packaged with the
"-tools" convention in Debian. On the one hand, we can see all the
convensions like "-utils", "-tools", and "progs" there.
Personally, I like the "-tools" convension for new ones.
Regards,
Ryusuke Konishi
next prev parent reply other threads:[~2009-07-30 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 16:29 proper name for userspace package? Eric Sandeen
[not found] ` <4A71CA72.8080106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-30 17:32 ` Ryusuke Konishi [this message]
[not found] ` <20090731.023234.56054455.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-07-30 17:50 ` Eric Sandeen
2009-07-30 18:36 ` Daniel Baumann
[not found] ` <4A71E82C.1040208-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2009-08-03 19:10 ` Ryusuke Konishi
[not found] ` <20090804.041006.12536354.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-03 20:04 ` Daniel Baumann
[not found] ` <4A7742D6.9050405-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2009-08-05 11:32 ` Chris Samuel
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=20090731.023234.56054455.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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