[EMAIL PROTECTED] wrote:
>> >> Hi, >> >> >> >> Thanks for your responses. >> >> >> >> that main guide seem to assume that I want to package a program, not a >> >> lib. >> >> >> > > (assume mainT guide) Well, the example is a program, but it's not really > > different from a library in terms of packaging. Or!? > > > I think you are pretty much right, except I`ll have to learn about the appropriate way to install a lib (where the shared object goes etc). > > > >> >> also, it makes some assumptions about the structure of my package >> >> release bundle. >> >> >> > > Not sure you're correct here, could you explain what you mean? > > > I was reffering to the source tar.gz >> >> how would you start debianizing it? >> >> >> > > Preparing the source is the first step. > > > > > >> >> must I first create a jnotify-ver.tar.gz file? >> >> >> > > Yes. Only keep the non-binary parts, Java packages tend to contain the jar > > libraries they depend on, you need to remove them and depend on the > > corresponding Java packages (if they're already in Debian, else you need > > to package them as well). If applicable in your case, I like to create a > > shell script which exports the CVS/SVN tree, removes everything not needed > > and create the .tar.gz. I then put it in my 'debian' directory, allowing > > others to recreate the sources from scratch. > > > Okay.. this part is done, I fixed my ant build to spit a tar.gz with the required files. since my library does not depend on anything, it was pretty straight forward. I`ll get back to the new maint guide soon. thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
