> > The name I choosed for the packages is: liblog4sh-shell. I guess it > > correctly > > reflects it's a library for the shell and it's name is "log4sh". Is this > > right? > > Looks fine to me. Nice. I keep it then. > available. So if this does work out cleanly, it would be cool if you > could make sure that all the documentation available in <package>/html > is also available either as plaintext file(s) or as manpage(s).
I forgot to mention I also included a plain text version. > > I tried to do the this by messing a bit with debian/<package.doc-base > > but didn't got it to work. Need some help on how to do this. > Just copy it to DESTDIR/usr/share/doc/<package>/html in the Makefile's > install target or (IMHO preferably) in debian/rules at about the time > the Makefile is called for the install target. Uhm. I'll experiment a bit with this, guess I got a clue. > Well, neither debian/rules nor the original Makefile should issue errors > during the build. If there is no "build" target in the Makefile, either > add it (empty) or remove the call to it in the build(-stamp) target of > debian/rules. I'll check this issue then. > > in Debian I guess gruler makes sense. Shoud i rename the package to > > 'gnome-screen-ruler'?? > > I personally wouldn't do that. Just keep the package name to gruler and > use Gnome Screen Ruler only where a longer project name or description > is sensible. Nice. So it stays that way. > Apart from the license issue (you should really ask debian-legal about > that), I wonder what sets it apart from logrotate? I've researched a bit this and Debian also includes vlogger and cronolog. I'll compare the feautes in more detail and make my mind if a debianized httplog makes sense. Antonio. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
