Re: Unparsable gcc version string? [WAS: lily 1.4.15]

To: bug-lilypond@gnu.org, debian-devel@lists.debian.org
Subject: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
From: Josip Rodin <joy@gkvk.hr>
Date: Tue, 2 Jul 2002 12:49:58 +0200
Message-id: <[🔎] 20020702104958.GB8531@cibalia.gkvk.hr>
In-reply-to: <[🔎] 871yambf1n.fsf_-_@peder.flower>
References: <15648.24300.89063.346207@meddo.cs.uu.nl> <15648.55397.503777.749196@wombat.chubb.wattle.id.au> <87d6u6bko4.fsf@peder.flower> <15649.27301.279592.346666@wombat.chubb.wattle.id.au> <877kkebh5k.fsf@peder.flower> <15649.31569.685205.152763@wombat.chubb.wattle.id.au> <[🔎] 871yambf1n.fsf_-_@peder.flower>

On Tue, Jul 02, 2002 at 12:27:32PM +0200, Jan Nieuwenhuizen wrote:
> AAARG!  How is anyone (being a humble configure script) supposed to
> pick `3.1.1<SPACE>20020606' to be the version string from that?

Why do you need the date, anyway? Just "3.1.1" should be enough, Debian
releases aren't meant to randomly break compatibility with the same version
and different dates.

-- 
     2. That which causes joy or happiness.


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

Follow-Ups:
- Re: Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Jan Nieuwenhuizen <janneke@gnu.org>

References:
- Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Jan Nieuwenhuizen <janneke@gnu.org>

Prev by Date: Unparsable gcc version string? [WAS: lily 1.4.15]
Next by Date: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Previous by thread: Unparsable gcc version string? [WAS: lily 1.4.15]
Next by thread: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Index(es):
- Date
- Thread