Hi,
so weeks ago I started looking into hobbit since one of my company's customers is using it. Of course the fact that it wasn't included in Debian so far was nagging me, so I took the packages from sf.net, used Henrik's debian/ dir as base for mine, and uploaded the packages.
http://packages.qa.debian.org/h/hobbit.html
Of course there's probably bugs in the packaging, so comments would be very welcome. The original packaging was already very usable, so many thanks for the great work.
There's also a hobbit-plugins package, but so far it only contains 2 plugins (an "apt" check, and a related check for upgraded libs still linked to running processes).
Hi Christoph,
On Sat, Sep 08, 2007 at 12:35:00AM +0200, Christoph Berg wrote:
so weeks ago I started looking into hobbit since one of my company's customers is using it. Of course the fact that it wasn't included in Debian so far was nagging me, so I took the packages from sf.net, used Henrik's debian/ dir as base for mine, and uploaded the packages.
thank You very much! I had been hoping someone would volunteer to be the Debian package maintainer, so this is very much appreciated.
There's also a hobbit-plugins package, but so far it only contains 2 plugins (an "apt" check, and a related check for upgraded libs still linked to running processes).
Good idea to put this in a separate package.
From a Debian viewpoint, the javascript to render the menu for the webpages wasn't free enough, so I wrote a replacement using CSS only. If that sounds interesting for inclusion into the next hobbit version, I can post the files here. (Or you can get them from ftp.debian.org.)
Excellent! I haven't looked at it yet, but it is certainly nice to have a truly open implementation for this.
Regards, Henrik
Re: Henrik Stoerner 2007-09-12 <20070912194736.GE22137 at hswn.dk>
thank You very much! I had been hoping someone would volunteer to be the Debian package maintainer, so this is very much appreciated.
Hi Henrik,
sorry for the late answer, I should move this mailbox to a more prominent place in mutt.
There's also a hobbit-plugins package, but so far it only contains 2 plugins (an "apt" check, and a related check for upgraded libs still linked to running processes).
Good idea to put this in a separate package.
The main "feature" I introduced here is a /etc/hobbit/clientlaunch.d/ directory where hobbit-plugins puts *.cfg files. It would be nice if "include" directories supported wildcards, at the moment the init script does something like "ls -1 /etc/hobbit/clientlaunch.d/*.cfg > /var/run/hobbit/clientlaunch-include.cfg" which is then included.
Excellent! I haven't looked at it yet, but it is certainly nice to have a truly open implementation for this.
Here's what I did:
- add a new menu.css file
- add a menu.cfg that contains the actual menu as a HOBBITMENU variable
- add "include /etc/hobbit/web/menu.cfg" to hobbitserver.cfg (just before BBMENUSKIN)
- tweak web/* to use &HOBBITMENU: sed -i -e's/ Transitional//' -e'/"Topline"/i&HOBBITMENU' $S/etc/hobbit/web/*_header (the Transitional removal is to fix the Doctype, iirc the CSS didn't work otherwise)
- do not install wwwfiles/menu/menu_items.js.DIST in hobbitd/Makefile
- remove <script> from hobbitd/webfiles/bb_footer and hobbitd/webfiles/hobbitnk_footer
(These changes are applied on the fly at package build time, having them included probably makes things easier.)
Christoph
cb at df7cb.de | http://www.df7cb.de/
On Friday 28 September 2007 11:52:49 Christoph Berg wrote:
Re: Henrik Stoerner 2007-09-12 <20070912194736.GE22137 at hswn.dk>
thank You very much! I had been hoping someone would volunteer to be the Debian package maintainer, so this is very much appreciated.
Hi Henrik,
sorry for the late answer, I should move this mailbox to a more prominent place in mutt.
There's also a hobbit-plugins package, but so far it only contains 2 plugins (an "apt" check, and a related check for upgraded libs still linked to running processes).
Good idea to put this in a separate package.
The main "feature" I introduced here is a /etc/hobbit/clientlaunch.d/ directory where hobbit-plugins puts *.cfg files. It would be nice if "include" directories supported wildcards, at the moment the init script does something like "ls -1 /etc/hobbit/clientlaunch.d/*.cfg > /var/run/hobbit/clientlaunch-include.cfg" which is then included.
I (maintainer of Hobbit for Mandriva) originally requested a feature like this, which Hendrik implemented using the "directory" directive, which will include all files in the directory (although I would have preferred a glob, to avoid /etc/hobbit/hobbitlaunch.d/somecheck.cfg.rpmnew, or /etc/hobbit/hobbitlaunch.d/somecheck.cfg~ being read and leaving the admin wondering why his new settings aren't applied).
In our packages, I ship both hobbitlaunch.cfg and clientlaunch.cfg with: directory /etc/hobbit/hobbitlaunch.d
since then one can be sure that client-side extensions will run on the hobbit server if installed and enabled by default.
Regards, Buchan
Re: Buchan Milne 2007-10-01 <200710011349.51274.bgmilne at staff.telkomsa.net>
I (maintainer of Hobbit for Mandriva) originally requested a feature like this, which Hendrik implemented using the "directory" directive, which will include all files in the directory (although I would have preferred a glob, to avoid /etc/hobbit/hobbitlaunch.d/somecheck.cfg.rpmnew, or /etc/hobbit/hobbitlaunch.d/somecheck.cfg~ being read and leaving the admin wondering why his new settings aren't applied).
Ah, I missed that so far in the documentation. The ability not to read files like *.dpkg-new is required for the include directory to be useful for us. Full-featured globbing is not necessary, I'm fine with a directory include provided it features something like "include only files ending in .cfg".
Christoph
cb at df7cb.de | http://www.df7cb.de/
participants (4)
-
bgmilne＠staff.telkomsa.net
-
cb＠df7cb.de
-
henrik＠hswn.dk
-
myon＠debian.org