Re: [multiarch] Proposal for *-dev packages
On Wed, Jan 14, 2004 at 09:32:18PM +0100, Goswin von Brederlow wrote:
> Daniel Kobras <firstname.lastname@example.org> writes:
> > On Wed, Jan 14, 2004 at 07:26:53PM +0100, Goswin von Brederlow wrote:
> > > 2. different header files per architecture
> > >
> > > The differences in the headers can be merged by using preprocessor
> > > conditionals.
> > How to include arch-specific information that is probed at configure
> That would be either static information that can be gathered once and
> hardcoded into the headers or its information particular to the buildd,
> which should never make it into the -dev package.
So you've just created:
- Another possible bug, since everyone installing from source builds
the headers on the target system. Who knows whether configure-time
information makes it into a header or not? There's a good chance the
Debian maintainer won't even notice.
- Another set of new packages, since almost every -dev contains
static libraries nowadays.
Solve the basic problem first and then deal with this sort of detail.
I personally think you can't do this without impairing the robustness
of package builds something terrible.
MontaVista Software Debian GNU/Linux Developer