Re: RFS: phpgroupware
On Wed, Dec 10, 2003 at 05:57:41PM +0000, Thomas Viehmann wrote:
> Jamin W. Collins (email@example.com) wrote:
> >I wouldn't drop the feature. After a purge, a package should leave the
> >system as close to the way it found as possible. There are users that
> >won't want the database around after a purge and there are those that
> >will. A simple prompt in postrm when purging for the DB admin password
> >should be fine. I realize we try to limit prompting to the bare
> >minimum, but if a user has indicated that they want to remove the
> >database on a purge, we need to be able to do so. This means we either
> >store the DB admin password in debconf (bad idea IMO) or prompt for it
> >when needed.
> OK. Sorry for misrepresenting (and misunderstanding) you, thanks for
> the clarification. On a side note: An alternative would be dropping
> the DB as the phpgroupware DB user and not deleting the corresponding
> (And, incidentally, with a cursory inspection of various postinsts I
> didn't find any examples.)
If the phpgroupware user had sufficient priviledges to drop the DB, yes.
However, giving the account that updates the DB the ability to drop it
may raise some other concerns.
While it might not be the best example, I do create and drop the
Mediamate database in it's package if the user has opted to have it
removed during purge.
> As for your suggestion of the upload to experimental:
> - If you prefer experimental, I don't mind. (Though I doubt that this will get
> the wide testing I seek.)
> - The thing is (and IMHO should be) one source package and thus all or nothing in
This could be handled by adjusting the debian/control and debian/rules
files as individual modules need to be added to unstable vs
> - I'm trying to replace phpgroupware in unstable (which has security holes etc.),
> thus I think that the users are better off with an update to unstable than with
> the removal of phpgroupware without substitute.
Another valid point.
> - The current version are perfectly OK to use. The only thing about "work in
> progress" is that I'll be changing some behaviour from the behaviour of the
> version presently in unstable to an "improved" (depending on your POV) version.
> (Example: The storage of the admin password will go.)
> - The work in progress is intended to be wrapped up rather soon. (As soon as other
> people are happy with it and the bug list is trimmed.)
> - Finally, I'd envision tracking phpgroupware 0.9.16 RC's in experimental once I'm
> satisfied with the packaging.
Jamin W. Collins
Remember, root always has a loaded gun. Don't run around with it unless
you absolutely need it. -- Vineet Kumar