[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-octave-devel] Bug#292917: needs to depend on f2c on m68k?



On 1 February 2005 at 17:50, Adam Conrad wrote:
| Dirk Eddelbuettel said:
| >
| > I am not aware of packages modifying debian/control on the fly. That
| > sounds a little fishy to me.
| 
| Are you sure about that?  All of my packages modify debian/control on the
| fly via substvars.  Sure, most just use shlibs:Depends, but others use

Sure -- I meant with direct brute force hacking of debian/control from
debian/rules as you suggest here. Not sure I know an example that does that.

| custom vars (like the PHP packages, using phpapi:Depends and
| apache:Depends, for instance).  That's what it's there for.  Certainly,
| some more complex packages also have substvars that are filled in on a
| per-architecture basis, as we're describing here.  Something like:
| 
| if [ `dpkg-architecture -qDEB_BUILD_ARCH` = "m68k" ];then \
| echo "m68k:Depends=f2c" >> debian/octave2.1-headers \
| fi
| 
| Before you run dh_gencontrol

Why don't you join the pkg-octave-devel team on alioth and test this then?

Dirk

-- 
Better to have an approximate answer to the right question than a precise 
answer to the wrong question.  --  John Tukey as quoted by John Chambers




Reply to: