On Thu, 9 Aug 2012, Stefano Lattarini wrote:
I am mostly worried about features that my package
currently depends on which have been announced to be deprecated for no
apparent reason, and without a sufficiently functional work-around, and
with only the sound of crickets chirping when these issue
Hi Bob.
On 08/08/2012 05:13 AM, Bob Friesenhahn wrote:
>
> [SNIP]
>
> I am mostly worried about features that my package
> currently depends on which have been announced to be deprecated for no
> apparent reason, and without a sufficiently functional work-around, and
> with only the sound of crick
On 08/08/2012 05:13 AM, Bob Friesenhahn wrote:
On Mon, 6 Aug 2012, Eric Blake wrote:
What _specific_ feature are you using from 1.12 that wasn't present in
1.11? Or put another way, either your configure.ac works equally well
with both versions (so you don't care which version), or there's
som
On Mon, 6 Aug 2012, Eric Blake wrote:
What _specific_ feature are you using from 1.12 that wasn't present in
1.11? Or put another way, either your configure.ac works equally well
with both versions (so you don't care which version), or there's
something you do with 1.12 that doesn't work with 1
On 08/07/2012 08:35 AM, Miles Bader wrote:
Ralf Corsepius writes:
Pardon, may-be I am missing something, but in my understanding I am
having the same issue as the OP:
No, you were just looking for an excuse to start ranting...
Feel free to think so ... EOT
Ralf Corsepius writes:
> Pardon, may-be I am missing something, but in my understanding I am
> having the same issue as the OP:
No, you were just looking for an excuse to start ranting...
-miles
--
"Yorton, Wressle, and Gospel Oak, the richness of your heritage is ended.
We shall not stop at y
On 08/07/2012 08:16 AM, Miles Bader wrote:
Ralf Corsepius writes:
My issue is <...rantrantblatherblather...>
Please start a new thread when your message has bugger all to do with
the previous message.
Pardon, may-be I am missing something, but in my understanding I am
having the same issue a
Ralf Corsepius writes:
> My issue is <...rantrantblatherblather...>
Please start a new thread when your message has bugger all to do with
the previous message.
Thanks,
-miles
--
The car has become... an article of dress without which we feel uncertain,
unclad, and incomplete. [Marshall McLuh
On 08/07/2012 01:36 AM, Eric Blake wrote:
On 08/06/2012 05:29 PM, Peter Johansson wrote:
Hi,
I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
time. I wonder is there's any documented macro that was introduced in
1.12 that I could use to m4_ifdef?
If nothing else, the aut
Hi Eric,
On 08/07/2012 09:36 AM, Eric Blake wrote:
On 08/06/2012 05:29 PM, Peter Johansson wrote:
Hi,
I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
time. I wonder is there's any documented macro that was introduced in
1.12 that I could use to m4_ifdef?
If nothing else
On 08/06/2012 05:29 PM, Peter Johansson wrote:
> Hi,
>
> I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
> time. I wonder is there's any documented macro that was introduced in
> 1.12 that I could use to m4_ifdef?
If nothing else, the autoconf philosophy of feature checks b
Hi,
I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
time. I wonder is there's any documented macro that was introduced in
1.12 that I could use to m4_ifdef?
Cheers,
Peter
12 matches
Mail list logo
