Feature #469
openTask #358: Better package our work
get dansguardian-squid preconfigured
70%
Description
I build a simple package for dansguardian.
http://svn.gna.org/viewcvs/doudoulinux/packages/trunk/tweaks/dansguardian-squid/ for the source
is it possible to move the configuration file and default banner from /live (Task #77) to this package.
The built dansguardian-squid is useless without these configurations files...
May be it is impossible because of Task #260 ?
May be there is another solution...
Updated by Jean-Michel Philippe about 13 years ago
I think we should make a DDL-specific package for these configuration files. The package dansguardian-squid doesn't refer to our project name because it supposed to solve a general issue that anyone could face while using Dansguardian with Squid: Squid and Dansguardian services must be restarted when network gets reachable.
The remaining files in live/
are specific to our use of Dansguardian:
I don't know right now how to package them. Should we make a small package for every package configuration? Should we make only one package, or a set of smaller packages per main functionality?
Updated by Jean-Michel Philippe about 13 years ago
- Due date set to 02/20/2012
- Target version set to 2012-02
- Estimated time set to 1:00 h
- Parent task set to #358
Updated by Jean-Michel Philippe almost 13 years ago
- Status changed from New to In Progress
- Assignee set to Jean-Michel Philippe
- % Done changed from 0 to 20
- Estimated time changed from 1:00 h to 10:00 h
Things are more complicated than expected… Currently I've packaged the standard Dansguardian configuration files in a new package named “ddl-tweaks-dansguardian”. It makes network now reachable, which was not the case before because Dansguardian refuses to start without having been configured. But the work is way not terminated…
First I'm facing dramatically low performances on web page loading on Efika. I started to change Dansguardian configuration and I think I should improve page loading of a factor around 10! The first version of the package will be available soon with this configuration.
Second, I figured out that several CD build scripts are dealing with Dansguardian. Some of them are translating strings written in configuration files (error messages, error web page, etc.). I have to port them to my new package and select the correct set of files considering the system language at install.
Finally, a way to improve performance is to avoid Dansguardian checks pages content against each available language. While this is not really an issue on quite recent computers, this could be on ARM. Moreover, as DDL gain more translators, we'll have more languages and then Dansguardian will need more time to check pages. I propose we introduce in the future debconf questions that allow to select which languages to check pages against at installation or while reconfiguring the package. New ticket wanted!
Updated by Jean-Michel Philippe almost 13 years ago
- % Done changed from 20 to 60
- Estimated time changed from 10:00 h to 12:00 h
Updated by Jean-Michel Philippe almost 13 years ago
- % Done changed from 60 to 70
Translation scripts have been moved from the live tree to the package. Testing required!
NB: we need to set the LANG variable in /etc/default/locale
while building the LiveCD since the chrooted environment doesn't have this variable set. It may moreover not be available to root.
Updated by Jean-Michel Philippe over 12 years ago
- Target version changed from 2012-02 to 2012-05
Updated by Jean-Michel Philippe over 12 years ago
- Due date changed from 02/20/2012 to 11/30/2012
- Target version changed from 2012-05 to 2012-11