On Tue, Jul 03, 2007 at 05:37:27PM -0300, Daniel Bolgheroni wrote:
> .if !${FLAVOR:L:Mno_mp3}
> MULTI_PACKAGES+=-mp3
> .endif
> .if !${FLAVOR:L:Mno_vorbis}
> MULTI_PACKAGES+=-vorbis
> .endif
>
> .if !${MULTI_PACKAGES:M-mp3}
> CONFIGURE_ARGS+=--disable-mp3
> .endif
> .if !${MULTI_PACKAGES:M-vorbis}
> CONFIGURE_ARGS+=--disable-vorbis
> .endif
>
> (...)
This is correct.
> If FLAVOR is specified at some point, it should modify some arguments of
> the build, not the subpackages itself. And vice-versa with SUBPACKAGE. Or
> am I completely missing the point?
You've run into some trickier aspects of package building.
Some flavors may influence the build, particularly trigger more building
time, and change the generated packages.
In the case of audio/bmp, activating mp3 and vorbis triggers the installation
of some more dependencies for the build, and more stuff gets built, hence
the build takes longer. As a result, there are more packages built. So
this is the sequence you see there.
What you haven't quoted is that no_mp3 and no_vorbis are marked as
PSEUDO_FLAVORS. This is tricky: those are flavors which influence the
build, but not necessarily the package itself. So, the main bmp package
is always the same, whether you specify no_mp3, or not. But FLAVOR=no_mp3
triggers a less complete build, with no -mp3 subpackage being built.
