* Alan McKinnon <alan.mckin...@gmail.com> wrote: > Some more: > > Don't depend on some arb version number of libs. Nothing worse than being > forced to use some lib 4 versions behind current when current actually works > just fine
ACK. But most times, that IMHO comes from incompatible API (or ABI) changes. Perhaps I should add some rules about that - libs have to maintain backwards API (or even ABI ?) compatibility, at least within the same major version. > No hardcoded locations. If I want to install to /opt/csw/package/, then I > should be able to do it, it makes zero difference to upstream if I do ACK. Packages should be (build-time) relocatable, following FHS-style classifications. > Maintain the README, NEWS, INSTALL, ChangeLog, etc. We users actually do read > them, and up to date metadata gives us a warm fuzzy where we feel good about > your code Well, separate changelog (beside the vcs' log) should only be required for large packages. Better a releas-notes file, stating everthing that's important for upgrades. BTW: meanwhile I've set up an sf.net project w/ maillist: https://sourceforge.net/p/oss-qm/home/ cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------
