On Sun, Dec 24, 2017 at 08:16:19PM +0100, Adam Borowski wrote:
> While autotools in principle do support out-of-tree builds, a particular
> program might still fail.
In practice, this is rare, unless the developer doesn't try to run "make
distcheck" before a build (like they really really should).
Osamu Aoki writes:
> maildrop source tree can be build with different build option to produce
> maildrop program in 2 ways for each arch.
> * set GID mail without restricted caller (maildrop)
> * set UID root with restricted caller for courier-mta
>(maildrop-courier) -- This is now missing
Hi Osamu,
On Mon, Dec 25, 2017 at 01:43:13AM +0900, Osamu Aoki wrote:
> Any pointer to a simple example which uses autotools as its build script
> is appreciated.
The rxvt-unicode source package generates three binary packages, each containing
a version of rxvt-unicode built with different config
On Mon, Dec 25, 2017 at 01:43:13AM +0900, Osamu Aoki wrote:
> maildrop source tree can be build with different build option to produce
> maildrop program in 2 ways for each arch.
>
> * set GID mail without restricted caller (maildrop)
> * set UID root with restricted caller for courier-mta
>
On Mon, 25 Dec 2017 at 01:43:13 +0900, Osamu Aoki wrote:
> Of course we can build 2 source packages to do this. But is there any
> easy clean way to do [two builds with different options] without making
> 2 source packages with identical upstream tarball.
>
> Any pointer to a simple example which
Hi,
maildrop source tree can be build with different build option to produce
maildrop program in 2 ways for each arch.
* set GID mail without restricted caller (maildrop)
* set UID root with restricted caller for courier-mta
(maildrop-courier) -- This is now missing in archive but we used to
6 matches
Mail list logo
