Re: Bug#696600: RFS: sun/0.2-1 [ITP] schedule cron or at-jobs at sunrise/set
On Sun, Dec 23, 2012 at 11:52:56PM -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 24 Dec 2012, Paul Wise wrote:
> > On Mon, Dec 24, 2012 at 7:45 AM, Steffen Vogel wrote:
> >
> > > There still the problem that the package name (sun) might be too generic
> > > to be included in the archive. What do you think about this concern?
> >
> > I think sun is the perfect name for this tool and there is no need to change it.
>
> It is indeed too generic. Better have a not-so-generic name NOW, than
> problems later.
There are two kinds of generic names:
* unrelated ("node" which has very vague ties with "manage a host (node)"
for HAM and no ties at all for javascript)
* related
For the latter, there's a valuable resource which needs to be shared between
potential users. If it's not used at all, it goes to waste. Of course,
end-user confusion is worse than having to type a bit more, so in doubt it's
better to not give the name to anything.
In this case, however, I see no other likely users: there's not much you
can do with Sun the day star on a computer shell, and there are no
legitimate uses related to Sun the part of Oracle (it'll be always something
more specific). So I'd say letting this package be named "sun" and use
/usr/bin/sun is warranted.
Like, a command-line utility of mine that can transcribe between language
scripts (cyrillic <-> latin <-> greek <-> furthark <-> hangul <-> ...) can
claim a legitimate stake to generic "transcribe", and a dubious but not
completely outlandish to its abbreviation "tran".
> I'd go with sun-cron
Incorrect and misleading. Using it for cron is only one of many possible
uses, and not even the primary one.
--
How to squander your resources: those silly Swedes have a sauce named
"hovmästarsås", the best thing ever to put on cheese, yet they waste it
solely on mere salmon.
Reply to: