On 13 June 2005 at 18:23, Steve Langasek wrote:
| On Mon, Jun 13, 2005 at 08:04:37PM -0500, Dirk Eddelbuettel wrote:
| 
| > On 13 June 2005 at 18:43, Santiago Vila wrote:
| > | On Mon, 30 May 2005, Dirk Eddelbuettel wrote:
| 
| > | > On 30 May 2005 at 14:20, Steve Langasek wrote:
| > | > | It would probably be better if r-base-dev simply specified "awk",
| > | > | which IIRC is "virtually-essential" by virtue of being a
| > | > | dependency of an essential package.
| 
| > | > I like that much better. So now the changelog stands at
| 
| > | >   * debian/rules: configure call with AWK="/usr/bin/awk"
| 
| > | This is fine.
| 
| > | >   * debian/control: Build-Depends on mawk | gawk | awk
| > | >   * debian/control: Depends for r-base-core on 'mawk | gawk | awk'
| 
| > | But this is not. Please don't do that. As it has been already pointed out,
| > | awk is essential, so any dependency or build-dependency on
| > | 'mawk | gawk | awk' is completely gratuitous.
| 
| > a) It actually is only required, and not essential:
| 
| >     [EMAIL PROTECTED]:~> apt-cache show mawk | head -2
| >     Package: mawk
| >     Priority: required
| >     [...]
| 
| base-files Depends on awk, which makes awk "virtually essential" (it's
| necessary for it to be virtually essential because awk is after all a
| virtual package, provided by multiple real packages).  Santiago is right,
| there really is no need to Build-Depend on awk or any of its variants here.

Oh well so my inkling was right. Whatever. [ And the 'virtually essential'
was not 'practically good enough', I suppose, as it did break on amd64 ... ]

But the fix is now in, and won't do any harm, so how about if we stop beating
this now-deceased horse and get on with other problems?  Just a thought ...

Dirk, while r-base_2.1.0.beta.20050613 is building

-- 
Statistics: The (futile) attempt to offer certainty about uncertainty.
         -- Roger Koenker, 'Dictionary of Received Ideas of Statistics'


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to