[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis



[Fiedler Roman, 2016-06-09]
> > * install into /usr/lib/logdata-anomaly-miner/ and dh_python2 will pick
> >   it up without any overrides, additional options, etc.
> 
> So I guess, before that (where dh_python2 refused to operate at all),
> using /usr/lib/aminer as a shorthand - as the package name is quite
> long - was a bad idea.

NAME in /usr/lib/NAME is not used in Python¹. It's not module name, you
cannot import it so Python module naming rules do not apply here.

[¹] at least in /usr/lib/NAME/foo scripts

> As import names cannot contain a dash, is use of
> "usr/lib/logdata-anomaly-miner/aminer" as module storage directory and
> "aminer" as shorthand module name in imports OK?

if /usr/lib/logdata-anomaly-miner is the storage and
/usr/lib/logdata-anomaly-miner/aminer is the module dir (with
__init__.py file), then yes

> Still when building, lintian is unhappy with the output package:
> 
> E: logdata-anomaly-miner: python-script-but-no-python-dep usr/lib/logdata-anomaly-miner/AMiner
> E: logdata-anomaly-miner: python-script-but-no-python-dep usr/lib/logdata-anomaly-miner/AMinerRemoteControl

is AMiner and AMinerRemoteControl symlinked in /usr/bin/?
(you can use debian/logdata-anomaly-miner.links to do that)


PS please don't CC me, I read debian-python@lists.debian.org
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


Reply to: