* Jake Goerzen <[email protected]> wrote: > I'm working on updating the CSWdovecot, CSWdovecot-devel, > CSWdovecot-sieve packages.
Good to see you digging in! In case you provide an updated package and take over dovecot, could you please continue to maintain changelog.CSW? ~skayser/bin/cswch is a little helper to do so. It's not that big of a task, but ultimately helps the sysadmins out there a lot to determine what exactly has changed between package revisions. > The current dovecot gar recipe creates a file collision with the sieve > plugin files between CSWdovecot and CSWdovecot-sieve pkgs. In the > recipe the GAR variable is set: > > PKGFILES_CSWdovecot-sieve = .*sieve.* > > I would expect this to put the right files in the CSWdovecot-sieve > package which it does, except the files are also put in CSWdovecot > package as well. Thus creating the file collision. Could well be due to the NOPACKAGE hack that I employed to mingle the two separate builds into one build description. Dago would now best. > A few possibilities > on how to move forward: > > 1) figure out how to get the recipe to do the right thing > > 2) move the CSWdovecot-sieve plugin into its own gar build recipe > separatly instead of the post-package hook > > 3) depreciate the CSWdovecot-sieve package since the sieve files are > already installed with the CSWdovecot package > > I like option 3 but I don't use sieve. However, sieve should work just > fine this way. Actually, I don't see a reason - besides the aforementioned hack - for the existance of a separate sieve (no additional deps e.g.). Should be fine to deprecate dovecot_sieve. Sebastian _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
