On 6 May 2005 at 00:29, Chris Lawrence wrote:
| On 5/5/05, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| > Agreed -- any idea why they differ from the default? I see mawk as
Priority:
| > required whereas gawk is merely Optional.
| >
| > Maybe that one wasn't built in a chroot but live on a box with gawk?
|
| Possible, or possibly the chroot wasn't clean...
|
| > | (there's no reason to use gawk). Is there a configure option in R to
| > | specify which awk is used? Build-Conflicts: gawk would work too, but
| > | it might be a little heavy-handed.
| >
| > Presumably I could specify it in the call to configure, but that should
| > amount to the same as calling for it in the Build-Depends.
|
| No, because 'Build-Depends: mawk' would still make it possible for
| gawk to be installed and found by configure (instead of mawk, which is
| always installed on a Debian system).
On 6 May 2005 at 00:29, Chris Lawrence wrote:
| On 5/5/05, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| > Agreed -- any idea why they differ from the default? I see mawk as
Priority:
| > required whereas gawk is merely Optional.
| >
| > Maybe that one wasn't built in a chroot but live on a box with gawk?
|
| Possible, or possibly the chroot wasn't clean...
|
| > | (there's no reason to use gawk). Is there a configure option in R to
| > | specify which awk is used? Build-Conflicts: gawk would work too, but
| > | it might be a little heavy-handed.
| >
| > Presumably I could specify it in the call to configure, but that should
| > amount to the same as calling for it in the Build-Depends.
|
| No, because 'Build-Depends: mawk' would still make it possible for
| gawk to be installed and found by configure (instead of mawk, which is
| always installed on a Debian system).
Yes, but by that same token you should be able (for now) to say AWK=mawk in
debian/rules which would override the AWK=${AWK-'gawk'} -- beauty of this
'use this values unless AWK already exists construct.
Dirk
--
An economist is an expert who will know tomorrow why the things he
predicted yesterday didn't happen today. -- Laurence J. Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
