unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alexey Abramov <levenson@mmer.org>
To: help-guix@gnu.org
Subject: Dovecot + pigeonhole packaging
Date: Wed, 28 Aug 2019 19:11:40 +0200	[thread overview]
Message-ID: <16cd93624e0.281d.da5dc967fe079fb386b94d5b80162893@mmer.org> (raw)

Hi guix,


My system requires me to have dovecot and pigeonhole. So I packaged it. I 
created two none public packages and merged them into one big package.


But wouldn't it be better to do it the same way as debian does?Every 
component lives in a separate package, and if I need some library I don't 
have to install the giant package.


The problem I encountered is that dovecot has mail_plugin_dir property 
which does not accept multiple folders. It means I have to put and install 
new plugins in the very same directory with existing plugins. rpath is not 
an option here. Even if a library knows where to load its dependencies, 
dovecot doesn't aware of it.


Is there a way to have shared store folder? Debian overrides  rpath to all 
dovecot extensions and set it to /usr/dovecot/lib.


Or maybe create a dummy package and use it as a storage for the libraries? 
What is the right approach here?


I also checked how nixos does it, and I don't like this approach, they 
patch source code and install their libs in /etc


--
Alexey

             reply	other threads:[~2019-08-28 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 17:11 Alexey Abramov [this message]
2019-08-29  6:01 ` Dovecot + pigeonhole packaging Gábor Boskovits
2019-08-30 19:46   ` Alexey Abramov
2019-09-01  6:37     ` Gábor Boskovits

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16cd93624e0.281d.da5dc967fe079fb386b94d5b80162893@mmer.org \
    --to=levenson@mmer.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).