Hi,

Quoting Daniel Schepler (2014-08-03 17:02:18)
> On Sun, Aug 3, 2014 at 2:15 AM, Felix Geyer <fge...@debian.org> wrote:
> > Is this already useful to apply? The syntax to conditionally drop
> > build-depends is not yet supported, right?
> 
> That's true, it won't yet build automatically.  But it's still
> definitely useful to reduce the manual work somebody would need to do for the
> bootstrapping.

while wookey can make a much more educated comment about the usability of this
patch from a bootstrapper's point of view, let me point out that the bug which
currently blocks packages with the new build profile syntax being uploaded to
the archive is #744246 and currently in the care of tech-ctte. You'll see that
the bug blocks a number of other bugs which are all bugreports carrying patches
that add the new syntax to packages. If it's okay for Felix then Daniel could
open a second bug with a patch that adds the <!profile.stage1> bit to
libqt4-dev and libcurl4-openssl-dev to not forget about this outstanding change
that goes in hand with the patch proposed in this bugreport.

> > The part about Qt 4 looks good.  I'm not so sure about using the bundled
> > libraries.  Adding a stage1 profile to curl seems like a cleaner solution
> > to me.
> 
> The problem here is that at this stage of a bootstrap, the krb5, ldap,
> etc. build dependencies of curl are not yet available, and
> bootstrapping curl without that support would create packages without
> equivalent functionality.  Which is something we try to avoid if at
> all possible.  I agree that using bundled curl for bootstrapping cmake
> isn't really pretty either, though.

You should also make sure that the binary packages that are built with the
bundled curl instead of the system curl expose no different functionality and
interfaces compared to the original binary packages. The reason is, that other
source or binary packages which depend on the cmake packages must find
everything they expect or otherwise this breaks the dependency system. Since
src:cmake does not build a shared library, using the bundled curl instead of
the system curl might work without problems.

You can read more about this requirement for build profiles in this section of
the spec:
https://wiki.debian.org/BuildProfileSpec#Profile_built_binary_packages

cheers, josch


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to