Re: announcing first release of common database infrastructure package
Hello On Mon, Mar 07, 2005 at 08:28:39AM -0500, sean finney wrote: hi martin, On Mon, Mar 07, 2005 at 01:23:51PM +1300, Martin Langhoff wrote: sounds really good. How do your scripts relate to the db management scripts provided by wwwconfig-common, maintained by Ola Lundqvist [EMAIL PROTECTED]? my code is a superset of what's done in wwwconfig-common. providing the scripts/code to manage databases is only half of the idea behind this project. the other half is providing a normalized method for doing so (that is, not just the scripts, but debconf questions, translations, and a pre-arranged set of code for each maintainer script). This sounds really great (as I'm the wwwconfig-common maintainer) ! I assume that this means that my plans to get rid of the wwwconfig-common package is in plan. I suspect your package should be either supercede wwwconfig-common or be rolled into it. this supercedes what's in wwwconfig-common. in fact, much of the underlying internal code is taken from or at least originally based on code from that package. Nice. There are two major parts of wwwconfig-common: 1) Database management, which now (finally) seem to be superseeded by another package. 2) Apache configuration, which is already superseeded as the apache configuration have support for config.d (etc) structure that make this part of wwwconfig-common unnecessary. I actually recommend people not to use it anymore. I think I have removed it from all my web packages, but I'm not sure. There are some other minor things like exim config but that has been superseeded a long time ago, as exim3 is not a default MTA. I greatly appriciate your work! For you who do not know. I wrote wwwconfig-common for one single purpose. To be a common part for the configuration of the imp and horde packages, so that I did not duplicate too much code there. And now quite a lot of packages use it. :) I have actually thought of splitting off the two parts of the configuration types to separate packages and creating a common configuration framework. I think I have mentioned this on mailinglists a couple of times. The problem is that I have not really done anything, so it has been just an idea for years. Best reagards, // Ola sean -- -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: announcing first release of common database infrastructure package
hi christian, On Mon, Mar 07, 2005 at 05:58:43PM +0100, Christian Perrier wrote: You might want to post a call for translations for the common templates in the package, as I understand this package includes a set of common templates. yeah, this project aims at making life easier for three distinct groups of people: the package maintainers, the local admins, and the translators. This can be made by just posting to debian-i18n with a pointer to the templates.pot file. You just need to give a bit of context so that potential translators know what this is all about (having a common set of templates for DB-related packages in order to avoid them translating the same thing over and over). okay, i'll do that some time in the near future. i'd like to give a final look over my templates to make sure that i like my own english before i ask anyone to translate it though :) I promise you'll soon get tons of translations in various languages and I'll personnally give some push so that translators know this is a really important thing to translate. thanks! sean -- signature.asc Description: Digital signature
Re: announcing first release of common database infrastructure package
Quoting sean finney ([EMAIL PROTECTED]): okay, i'll do that some time in the near future. i'd like to give a final look over my templates to make sure that i like my own english before i ask anyone to translate it though :) Well, be sure that we will be critic towards your English too...even if mine isanything but perfect (by far). More specifically, having the templates compliant with the Debconf Templates Style Guide (cf devel reference) is a must have, of course -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: announcing first release of common database infrastructure package
Quoting sean finney ([EMAIL PROTECTED]):
to reply to my own post...
i was under the impression that because dbconfig-common was previously
in experimental that i wouldn't have problems related to the stalled
NEW queue, but i was wrong.
so you can get them here:
deb http://people.debian.org/~seanius/policy/examples/ ./
deb-src http://people.debian.org/~seanius/policy/examples/ ./
you want version 1.4.
Well, IN finally had a look at the debconf templates...
Comments about the templates:
--
If no longer have need of the data being stored by ${pkg}, you
should answer yes. If you want to hold this data for another
time, or if you would rather handle this process manually,
anwer no.
--
(typo detected, btw)
You should avoid making reference to specific user actions such as
answer yes for boolean templates. Depending on the interface and
interface translation, the user may be presented with something else
than yes/no choices for boolean templates, such as a check box.
The recommended wording in such case is If you choose this option,
blah blah or (for if you answer no) If you refuse this option,
blah blah.
--
_Description: Passwords do not match!
Sorry, the passwords you supplied do not match. Please try again!
--
I usually recommend avoiding exclamation marks as well: Passwords do
not match! should be replaced by Password mismatch. I also tend to
discourage the use of Sorry for more factual wording. In general,
anything suggesting that the computer behaves like a person should be
discouraged (the infamous use of first person which some maintainers
enjoy). Neutral and factual wording is the key point.
A few initial capitals are also missing here and there
Another one:
--
Template: dbconfig-common/mysql/host
Type: select
Choices: ${hosts}
_Description: What host is running the mysql server for ${pkg}?
Please select the remote hostname to use, or select new host to
enter a new host.
--
I usually recommend opened prompts for select and string
templates and leave interrogative form to boolean templates.
_Description: Host name of the MySQL database server:
(MySQL should be spelled that way, IIRC)
_Description: What should be the mysql database name for ${pkg}?
becomes:
_Description: MySQL database name for ${pkg}:
Template: dbconfig-common/mysql/app-pass2
Type: password
_Description: Please re-enter the password
Please re-enter the password.
--The long description here is useless. You can safely remove
itor provide something more explicit. Indeed I would write that
one like this:
Template: dbconfig-common/mysql/app-pass2
Type: password
_Description: Password confirmation:
Last (but not least), a few lines in the templates file end with extra
spaces...these should be removed as they create double spacing inside
sentences.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: announcing first release of common database infrastructure package
On Tue, Mar 08, 2005 at 10:51:48PM +0100, Christian Perrier wrote: Comments about the templates: wow... thanks for all these. i'll work on incorporating these suggestions in with the next version, before i make a request for translations. sean -- signature.asc Description: Digital signature
Re: announcing first release of common database infrastructure package
hi martin, On Mon, Mar 07, 2005 at 01:23:51PM +1300, Martin Langhoff wrote: sounds really good. How do your scripts relate to the db management scripts provided by wwwconfig-common, maintained by Ola Lundqvist [EMAIL PROTECTED]? my code is a superset of what's done in wwwconfig-common. providing the scripts/code to manage databases is only half of the idea behind this project. the other half is providing a normalized method for doing so (that is, not just the scripts, but debconf questions, translations, and a pre-arranged set of code for each maintainer script). I suspect your package should be either supercede wwwconfig-common or be rolled into it. this supercedes what's in wwwconfig-common. in fact, much of the underlying internal code is taken from or at least originally based on code from that package. sean -- signature.asc Description: Digital signature
Re: announcing first release of common database infrastructure package
anyway, i've uploaded my first public release of dbconfig-common to experimental. minus a couple bells and whistles (and probably plus a bunch of undiscovered bugs), it's pretty much feature complete for what's mentioned on my webpage[3], so at this point i'd like to call for some brave volunteers. You might want to post a call for translations for the common templates in the package, as I understand this package includes a set of common templates. This can be made by just posting to debian-i18n with a pointer to the templates.pot file. You just need to give a bit of context so that potential translators know what this is all about (having a common set of templates for DB-related packages in order to avoid them translating the same thing over and over). I promise you'll soon get tons of translations in various languages and I'll personnally give some push so that translators know this is a really important thing to translate. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: announcing first release of common database infrastructure package
On Mon, 7 Mar 2005 08:28:39 -0500, sean finney [EMAIL PROTECTED] wrote: my code is a superset of what's done in wwwconfig-common. That sounds great! thanks for your work on this front. I'll be reading your doco in more detail, as I have to sort out the path forward for twig... martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: announcing first release of common database infrastructure package
Sean, sounds really good. How do your scripts relate to the db management scripts provided by wwwconfig-common, maintained by Ola Lundqvist [EMAIL PROTECTED]? I suspect your package should be either supercede wwwconfig-common or be rolled into it. cheers, martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
announcing first release of common database infrastructure package
hey folks, you might remember some time ago i started a thread[1] or two[2] about developing a consistant policy/feel for how database (more specifically rdbms) application packages should work. well, since then i've spent a lot of time working on both a 'best practices' document as well as a debian developer toolkit for easily implementing the previously mentioned suggestions. dbconfig-common abstracts almost 100% of the database-maintainance related work into a common package that can be used by any package maintainer. it consolidates efforts, code, and bugs into a single more easily maintainable place, provides for an easier experience on the part of the developer, and a more integrated experience for the end-user/admin. anyway, i've uploaded my first public release of dbconfig-common to experimental. minus a couple bells and whistles (and probably plus a bunch of undiscovered bugs), it's pretty much feature complete for what's mentioned on my webpage[3], so at this point i'd like to call for some brave volunteers. anyone who is tired of having to spend hours maintaining their home-rolled mysql/pgsql mangement maintainer script code is whole heartedly encouraged to check this out! sean [1] http://lists.debian.org/debian-devel/2004/10/msg00340.html [2] http://lists.debian.org/debian-devel/2004/10/msg00962.html [3] http://people.debian.org/~seanius/policy/dbconfig-common.html -- signature.asc Description: Digital signature
Re: announcing first release of common database infrastructure package
to reply to my own post... i was under the impression that because dbconfig-common was previously in experimental that i wouldn't have problems related to the stalled NEW queue, but i was wrong. so you can get them here: deb http://people.debian.org/~seanius/policy/examples/ ./ deb-src http://people.debian.org/~seanius/policy/examples/ ./ you want version 1.4. thanks, sean -- signature.asc Description: Digital signature
Re: announcing first release of common database infrastructure package
On Friday 04 March 2005 23.57, sean finney wrote: anyone who is tired of having to spend hours maintaining their home-rolled mysql/pgsql mangement maintainer script code is whole heartedly encouraged to check this out! *applaudes heartily* That's sorely needed. Now I hope that the point where we (Debian users) can actually just apt-get install db-using application and it will Just Work(tm) is right around the corner. (Yeah, I know, some maintainers of database-using packages already have this working.) greetings -- vbi -- Today is Prickle-Prickle, the 64th day of Chaos in the YOLD 3171 pgp7RA4QjQ4IN.pgp Description: PGP signature
