Lirc 0.8.5-1fremantle30
Lirc server
Internal lirc server.
Section:
utils
Repository:
Depends:
Size:
291504 bytes
MD5sum:
6b3c16150ad6de3027757033bce43d31
Source:
Status:
Promotion cancelled
Bugtracker:
QA Quarantine ends:
ENDED 2010-03-04 11:15
Packages depending on this package:
Changes
| Version | Changes | Author | Date |
| 0.8.5-1fremantle30 | * Bug tracker link added. | Niko Rehnbäck | 2010-02-22 08:34 UTC |
Package events
| Event type | User | Timestamp |
| Package is in testing | System | 2010-02-22 11:15 UTC |
Comments:
Now its utils, just took some time i guess.
Did those things but that section still seems to be user/multimedia, any ideas what went wrong ?
Thank you for those useful tips, I will make new package later today after school.
One more question: will autobuilder put the new package to extras-devel or extras-testing now that the package has been promoted or do I have to promote the new package again ?
Section could be "utils" like it's in debian.
Optifying is easiest with placing "auto" to debian/optify, then autobuilder will run maemo-optify-deb for the deb package before sending it to repository.
Should the section just be opt/ ? Are there any other changes needed to make ?
That's exactly why this should not be in user/* category. I don't think that there are many people who would like to install lirc alone. It will also make simpler for you real app, qtirreco, to pass QA queue when this packagae is not stuck with (quite likely) negative votes.
This package could also be optified.
If a package depends on lirc then it's automatically installed like you said.
Do we need this user/ section? Shouldn't it rather get automatically installed by depends: of any lirc using application?
Comments:
You must be logged in to make comments.