Quote:
Really:) |
Quote:
|
Thanks to everyone for the great suggestions. I finally settled on just using 'pkg-check'. I'll attach here a copy of the first 'release'. It's not really exhaustive in what it does, but is handy anyway.
The program notifies you of any unusual content in already-created packages or directories with raw package content. It can be used for slackware-style *.txz packages, *.rpm or *.deb package archives. Using pkg-check is completely non-destructive -it only reports and makes no corrections or changes to package or directory content. The command 'pkg-check --help' will show the help page. Code:
#!/bin/bash |
I see you have to run it as root or it complains about file ownership. Not a complaint, just wasn't obvious to me at first as I do not think this is the case with lintian or rpmlint, IIRC.
EDIT: Perhaps pkg-check should issue a warning if it was not run as root, saying that file ownership checks may not work correctly. Or you could do ownership checks by reading the output from a verbose tar (or cpio in the case of rpm) listing of the archive, which would allow non-root users to run it. |
I think you should be checking that the directory naming matches that of tar 1.13, i.e. internally the tar should have directories formatted like this:
Code:
./ Code:
|
You might want to do some checks on the formatting of slack-desc itself, e.g. line length and that the first line is formatted with correctly, so that it displays correctly when --terse is used.
|
Thanks for the suggestions -I knew there would be more things to (maybe) do. As commented in the code, it would be useful to check symlinks for hard-coded paths and/or symlinks which appear to be faulty or point to locations not included in the package. I may be able to get around needing to be root for it to be quiet when all is really okay with owner/group.
|
This was a really nice idea. Anything further ever happen with it or is it on hold for now? I can understand if it is as you are doing this stuff for free. Just wondering? ;)
P.S. If you are still working on it you might want to consider adding a warning/error if you try to make a package with spaces in the symlink path? They may point to valid locations but will not work in Slackware packages (as of right now). |
I vote for the name
inspector-gadget |
If you scroll up you will see he already went for the name pkg-check so the original request is solved. Now we (or at least I) are asking about exact functionality.
|
Epic slacktroll is epic. ;)
Regards. |
Good idea, ruario. In fact it would be good to indicate any object with spaces in the name. I'll get on this soon -I'm a kind-of winter-of-code guy... have you been using pkg-check?
|
Quote:
|
All times are GMT -5. The time now is 05:50 PM. |