On Fri, Aug 2, 2013 at 2:55 PM, Pierre Schmitz <pie...@archlinux.de> wrote: > Am 02.08.2013 14:14, schrieb Bartłomiej Piotrowski: >> On 2013-08-02 08:41, Pierre Schmitz wrote: > > If you abuse the split package this way, you still have to rebuild and > publish both split packages if e.g. the passenger module requires a > rebuild. Yep. We will drop the split package.
> In general I am not sure if there is a sane way to package these build > time modules. It would be impossible to cover all the combinations and > external "modules" a user might want. Is it a good idea to provide a > separate package that has all kinds of different modules built in? There is no perfect solution with build time modules. It's broken by design. > Probably not. And people who need certain non-standard modules are > better off compiling their own package. > > I would probably provide a vanilla package with sensible defaults and > make it easy for people to extend on that. So, I think we'll rollback to one package co-maintained by Bartholomej and me, with interesting optional modules and auth-pam (I use it). Nothing should block a nginx update, so if auth-pam is incompatible, it will be dropped. Passenger external module will be dropped as it causes too frequent rebuild. -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A