Hello,thanks for the reply, I have a working beta since several months now, but had to put it aside for a while. Now I would like to publish it on CPAN.code is already here: https://github.com/ANSI-C/realtimed I would go for Linux::Daemon::Realtimed for the name, and since I have this module directory structure:
and given that I never released a daemon module before, I would like to have couple advises from you, if possible: - this module after the first run does configure itself as a systemd service (giving instructions to enable by default if wanted), is it correct to put the actual daemon code under bin ?- is it ok to put in lib just the POD documentation ?- README.pod is a symlink to POD under lib just because GitHub automatically displays only a README in the root dir, is that ok for CPAN standards ?- is there a standard way for CPAN to add module bin dir to user's PATH ? Thank you in advance for the advises you may give. Anselmo On Mon, 2020-07-06 at 12:08 +0100, Neil Bowers wrote: > Hi Anselmo, > > > […] as long as CPAN name is concerned, I am dubious about the name, > > this daemon works only on Linux, due to inotify system call usage, > > and it is a single executable, so I thought about these possible > > names: > > • App::Realtimed > > • App::Linux::Realtimed > > • Linux::App::Realtimed > > • Linux::Daemon::Realtimed > > • Daemon::Linux::Realtimed > > • Linux::Realtimed > > • Realtimed > > the last two ones seems preferable > > > We strongly discourage the use of top-level namespaces like > "Realtimed". And given it’s Linux specific, a name beginning with > Linux:: makes sense. I’d go with either Linux::Daemon::* or Linux::* > > > > From the description of incrond — which I’m not at all familiar with — > maybe something like Linux::FileMonitor might also work, as that seems > to be what it does (monitor files and then invoke commands triggered > by events on the files?) > > > > > In case, can you reserve to me the chosen namespace? > > > We don’t reserve namespaces. > > > > Once you’ve picked a name, you could sketch out your design in code > and do a placeholder release, with a caveat at the head of the > DESCRIPTION section in the doc. Then you’d get the first-come indexing > permission assigned to you for the top namespace of your app. > > > > But to be honest, I suspect you could just go ahead and develop it, > and it’s unlikely anyone would have bagged your chosen namespace in > the meantime. > > > > Cheers, > > Neil > > > > > > > >
