PICCORO McKAY Lenz writes:
> The current versions can be built directly to installable .debs from the > source tarballs, although this was done on Ubuntu. It's very likely to work > on Debian, although I have not checked. Note that going that route requiresFor you SAM unfortunatelly this will break many things on debian for upgrades..
My .deb packages are not upgrades. They are alternate builds.Besides, nobody is forced to do anything. Everyone is free to stay on the Debian's existing packages. But if they want to build .debs directly from the released tarball, that's the cost of doing so.
Debian packages do not include maildrop and sqwebmail subpackages. Instead maildrop and sqwebmail get built from their own tarballs. And, periodic someone comes in here wondering about subtle issues because of that. This is an error in Debian's packaging.
Also, I don't see a webadmin subpackage, perhaps webadmin is included in the main one, but it should be a subpackage. Also my package builds separate subpackages with the apache configuration. If apache is installed, installing Courier automatically installs apache configuration files, all that's needed is the a2enconf command to enable sqwebmail, mlm, and webadmin.
Perhaps Debian's main courier/sqwebmail packages manually install apache configuration files, if apache is already installed. Even if they do that, the subpackage-based approach is just so much better, in many ways. For example: if apache is not initially installed, but gets installed later, then installing the apache subpackages will automatically configure sqwebmail/mlm/webadmin. A subpackage-based approach for this is, in my view, undisputably better.
> rebuilding all dependencies, courier-unicode and courier-authlib; as well as> uninstalling and purging the old debs. These debs are not compatible with > the Debian-provided ones.i do not recommend this unless such packages can be in sync with debian ones...
My packages are not meant to be in sync, but be an alternate build. Choice is good, it's never bad.
but seems you SAM neither the debina packager are in sync ...
My packages's purposes is not to be synchronized with Debian ones'.
debian has a EXCELLENT upgrade and maintenance system, your packages
I don't know what that means. My packages get built directly from the source tarball, and new versions, once they release and come out, should build directly into updated .debs, that will update via apt, normally, just like any other package. You can put them in your local apt repo, using aptly or similar, and 'apt upgrade' will pull them in just like any other deb.
It's really a simple as tar xf courier-<version>.tar.bz2 cd courier-<version> sh -vx ./courier-debuild mv deb/*.deb <somewhere> sudo apt update sudo apt upgradeWrite a script that does something like this, and then puts the resulting built debs into your local apt repository, that's already configured in sources.list. That's just a one-time setup. Now, you've got a turnkey system that can quickly update to a new release, without waiting for Debian's packaging to catch up.
just removes and put new files.. does nto take care of the system changes respect non-system changes,, in resume those pacakges you recommend to use are not good for production sites
My packages will update just fine on their own, but they are not meant to update Debian ones. This is an alternate build, whose configuration is aligned closer to the package's defaults, rather than Debian's.
pgpv3LzTrxB5M.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
