Repost: RFC and preliminary RFS: prayer webmail
I try this again since I never got any response back in November... I have now created a working prayer package. It's not finished, but good enough to show you, fellow list subscribers. You can find it at: http://www.kibibyte.se/download/debian/ DSC: http://www.kibibyte.se/download/debian/prayer_1.0.18-1.dsc Please see the ITP at http://bugs.debian.org/392823 for the full story. The source package builds two packages: prayer and, for completeness, prayer-accountd, although the latter is still pretty useless outside Cambridge. Note: the prayer binary package uses libc-client2006b from experimental, but the dependency is missing from the control file. You will probably want to build the source package, after inspecting it, anyway. 2. Support for other character sets than ISO-8859-1 is non-existant. Conversion of various mail text to UTF-8 has to be added. I have now addressed this as well as modified UTF-7 encoding and decoding. See README.Debian. 5. At least minimal man pages have to be written. I have not addressed this yet. Please disregard for now. Something I've been thinking about: If two packages share a /var/(lib|run|log) subdirectory, how do you know when to remove it? I reckon that it should be removed when the last of the packages has been purged. Both packages place files there at runtime, so dpkg won't remove it since it's nonempty. But you can't just remove it in postrm if it's empty. Do you: a) leave it alone; let root delete it manually when it's no longer needed b) use dpkg -S to see if it's still in use c) use dpkg -l to see if the other package is still installed d) avoid sharing directories under /var e) do something else? Thank you for your interest! -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpy36P5BBFo6.pgp Description: PGP signature
Re: Repost: RFC and preliminary RFS: prayer webmail
On Sat, Mar 10, 2007 at 08:05:55PM +0100, Magnus Holmgren wrote: Something I've been thinking about: If two packages share a /var/(lib|run|log) subdirectory, how do you know when to remove it? I reckon that it should be removed when the last of the packages has been purged. Both packages place files there at runtime, so dpkg won't remove it since it's nonempty. But you can't just remove it in postrm if it's empty. Do you: a) leave it alone; let root delete it manually when it's no longer needed b) use dpkg -S to see if it's still in use c) use dpkg -l to see if the other package is still installed d) avoid sharing directories under /var e) do something else? The easy thing to do is to include it in the package, rather than creating it in maintainer scripts. Then dpkg leaves it alone if another package also includes (and in recent releases may even succeed in not warning you). I think there are cases where it is advantageous not to include it, but they don't occur to me presently.. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Repost: RFC and preliminary RFS: prayer webmail
On Saturday 10 March 2007 21:37, Justin Pryzby wrote: On Sat, Mar 10, 2007 at 08:05:55PM +0100, Magnus Holmgren wrote: Something I've been thinking about: If two packages share a /var/(lib|run|log) subdirectory, how do you know when to remove it? I reckon that it should be removed when the last of the packages has been purged. Both packages place files there at runtime, so dpkg won't remove it since it's nonempty. But you can't just remove it in postrm if it's empty. Do you: a) leave it alone; let root delete it manually when it's no longer needed b) use dpkg -S to see if it's still in use c) use dpkg -l to see if the other package is still installed d) avoid sharing directories under /var e) do something else? The easy thing to do is to include it in the package, rather than creating it in maintainer scripts. Then dpkg leaves it alone if another package also includes (and in recent releases may even succeed in not warning you). I think there are cases where it is advantageous not to include it, but they don't occur to me presently.. The directory is included in the packages, that's why I wrote that dpkg won't remove it. The problem is that postrm purge is called after dpkg removes the last of a package's files. Thus we have to delete not only the files, but also the directories, that are not deleted already in postrm remove. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) Exim is better at being younger, whereas sendmail is better for Scrabble (50 point bonus for clearing your rack) -- Dave Evans pgptCZeun87T4.pgp Description: PGP signature
Re: Repost: RFC and preliminary RFS: prayer webmail
On Sat, Mar 10, 2007 at 10:19:57PM +0100, Magnus Holmgren wrote: On Saturday 10 March 2007 21:37, Justin Pryzby wrote: On Sat, Mar 10, 2007 at 08:05:55PM +0100, Magnus Holmgren wrote: Something I've been thinking about: If two packages share a /var/(lib|run|log) subdirectory, how do you know when to remove it? I reckon that it should be removed when the last of the packages has been purged. Both packages place files there at runtime, so dpkg won't remove it since it's nonempty. But you can't just remove it in postrm if it's empty. Do you: a) leave it alone; let root delete it manually when it's no longer needed b) use dpkg -S to see if it's still in use c) use dpkg -l to see if the other package is still installed d) avoid sharing directories under /var e) do something else? The easy thing to do is to include it in the package, rather than creating it in maintainer scripts. Then dpkg leaves it alone if another package also includes (and in recent releases may even succeed in not warning you). I think there are cases where it is advantageous not to include it, but they don't occur to me presently.. The directory is included in the packages, that's why I wrote that dpkg won't remove it. The problem is that postrm purge is called after dpkg removes the last of a package's files. Thus we have to delete not only the files, but also the directories, that are not deleted already in postrm remove. dpkg will remove it, if it's included in the package, if there are no conffiles (this [should] only happen[s] when it's in /etc) or other dpkg files, and (naturally) if it's empty. I think the recent change for etch was to retry removal of non-shared directories for which removal failed during remove during purge and only warn if they failed both times. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
