On Thursday 17 December 2009 15:41:58 Pedro Lopez-Cabanillas wrote:
On Thursday, December 17, 2009, Will Stephenson wrote:
On Wednesday 16 December 2009 17:00:02 Pedro Lopez-Cabanillas wrote: Package naming - it's conventional to use lower case names for your packages (even the Build Service packages, when the specfile creates lower case rpms) eg kmetronome, kmidimon, if only because your packages will appear with other kde packages in a case-sensitive sort. CamelCase package names are generally a sign of delusions of grandeur, eg NetworkManager. You can rename a package by copying it with osc copypac and then delete the old package.
I am thinking about creating several sub-projects: * qt4 for my Qt4-only based packages: vmpk and aseqmm * kde for the KDE4 packages: KMid2, KMetronome and KMidimon
Is there a reason why these should be separate? I would combine them and set various KDE4:* repositories eg vanilla 11.2, Factory:Desktop, etc.
* kde3 for Kaseq, which is not yet ready for KDE4 migration
good idea, base on KDE:KDE3 repos.
What do you think? While moving the packages from the old to new locations, they would be properly renamed as well.
From the rpmlint reports:
aseqmm: Only the package containing the shared library needs the library major version as a suffix. I suggest: libaseqmm0 (libaseqmm0.so.0*) libaseqmm-devel (headers) aseqmm (programs, other files like README) aseqmm-debug*
I would like to add a -doc package for the doxygen generated documentation which is not packaged right now. What name would be better? libaseqmm-doc?
libaseqmm-doc if it is specific to the library, otherwise aseqmm-doc cheers Will -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org