On Wednesday 30 May 2007, you wrote: [snip] | Hmm. I'm not sure about the package name - http is a VERY crowded | namespace and a lot of users would assume some kind of Apache | connection with this package. I went ahead and renamed it libemhttp and added the -dbg and emhttp-tools as well. | Which package(s) are going to depend on this library? plucker-desktop (v1.9) that is in the upstream SVN requires this library in order to build the desktop. Right now Debian isn't building the desktop due to issues with it and this library helps curb that issue. | The binary should specify the SONAME: libhttp0 or libhttp1. The source | package is fine. I fixed this, the SONAME is libhttp0 (libhttp.so.0). | You should also provide a -dbg package for all libraries (you also | haven't specified the language used in this project - the code samples | in the txt file are all C). -dbg packages are likely to become mandatory | in due course to provide a complete debug chain. In an embedded context, | these would be used inside a chroot on the workstation (debugging on an | iPAQ isn't fun.) Added the dbg package. [snip] | Your website txt file mentions embedded use (hence my interest as | DD & Emdebian developer and iPAQ/GPE developer) but remember that this | is not simply going into Emdebian or some limited repository just for | embedded packages. It is going into Debian with 19,000 other packages. | Let's just say that most of the short names have been taken. ;-) | | It would be VERY handy to convert that txt file into the simplest of | HTML and link to it from the homepage. (It's also v.long for a txt file | so it would be best to split it into general, usage, history and API | pages). Nothing fancy, just wrap in <html><body> </body></html> and | wrap each paragraph in <p></p> and maybe use a few <h1></h1> lines. Just so you know this isn't my library or my site, so I can't do that with the http.txt file, what I did though was add it to the description. | I'm willing to take a closer look at it and potentially sponsor it - | BUT the package name must be changed first, IMHO. Name is fixed, but there may be some more things yet to fix. This is my first library package and I am super new to this. [snip] | The other problem is that you appear to make this CPU-specific - I | think this should be made much clearer. Exactly which CPU's are | supported and which are not? I have the Architecture set to any. It builds out on i386 and amd64 here. [snip] | Maybe rename the source package as emhttp-tools. The main package | provides the binaries which depend on libemhttp0 and this ONLY contains | the shared library, built from the one source package (along with the | -dbg and -dev). i.e. you should be making FOUR binary packages from | this tarball: | | emhttp-tools: /usr/bin/* | libemhttp0: /usr/lib/ | libemhttp-dev: /usr/include usr/lib/pkgconfig (if used) and the other | components of a normal -dev. | libemhttp-dbg: /usr/lib/debug/usr/lib This has been fixed as well. If there are any required changes I can fix them up. | Debian will add other bits like ChangeLog, copyright and manpages for | each of those binaries. Emdebian will remove all of those and | cross-build suitable binaries. | | On a final note, I haven't looked at the package yet but I would | STRONGLY recommend CDBS for this package. It makes automated | cross-builds trivial. Whatever you use, *please* do not use highly | customised rules in debian/rules. As a package directly targetting | embedded uses (and which has very, very little benefit to a desktop | machine) it is only sensible to ensure that it cross-builds (within | Debian) as easily as possible. See http://wiki.debian.org/EmdebianGuide | (Adding cross-build detection section.) I am using CDBS. First time actually and I never realized just how easy it makes things. Neil, I appreciate your help and your possible sponsorship once this package is ready. If you have anymore comments, questions, or concerns, please do not hesitate to contact me. -- Richard A. Johnson nixternal@ubuntu.com GPG Key: 0x2E2C0124
Attachment:
signature.asc
Description: This is a digitally signed message part.