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

packaging review (lintian clean)



Hello all, 
 
Could I get a packaging review?  My first time building/bundling a script for debian (debian-native) and I want to make sure I get the "right advice" on a few points:
 
1) Is the use of tempfile here correct? (is this properly secure / policy compliant? should it be in /var/run?  but /var/run requires permissions issues)
 
https://github.com/ramses0/xscreensaver-pi-hdmi/blob/master/bin/xscreensaver-pi-hdmi#L22
 
2) Control file - does this look right? I removed the initial ${misc:Depends} which I'm assuming was from *.substvars?  Is there more specific documentation on control-file syntax?  Does everything else look right?
 
https://github.com/ramses0/xscreensaver-pi-hdmi/blob/master/debian/control     
 
3) Not checked in are: debian/files, debian/*.substvars, debian/*.debhelper.log ... are they required, or transitory?
 
4) Use of debian/README.md as double/triple-duty (manpage, documentation, github initial page)... i'd prefer to have it at top level, but i think debian likes to have it in the debian directory.  Is there another project I can look at which is doing this successfully?  I don't want to use symlinks, but I'd prefer to have it in one place.

5) This package is technically targeting "raspbian" in that it solves a specific issue related to HDMI ports and screensaver on Raspberry PI machines.  I have an architectural question listed in the README at the end: this is working around "some issue" that is normally handled somewhere else in the software stack.  Is it an HDMI/kernel issue that the port isn't deactivated?  Is it xscreensaver that should be deactivating the port?  I don't know enough about the "deepness" of the issue to make a better decision than pulling together this package.

Thanks!

--Robert


Reply to: