[Top][All Lists]

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


From: olafBuddenhagen
Date: Fri, 23 Jul 2010 11:24:34 +0200
User-agent: Mutt/1.5.20 (2009-06-14)


On Mon, Jul 19, 2010 at 10:57:48AM +0200, Thomas Schwinge wrote:
> On Fri, Jul 16, 2010 at 12:19:21PM +0200, Emilio Pozuelo Monfort wrote:

> >     * hurd/version.h (HURD_INTERFACE_VERSION): Bumped for the
> >     recently added RPCs.
> I don't see a need for doing this unless you conditionalize anything on
> the increased version number.  The only example that I can find where
> this is done, is [glibc]/sysdeps/mach/hurd/configure.in for the ``new
> Hurd RPC interfaces supporting 64-bit file sizes'' (ChangeLog.13).
> Perhaps we should get rid of this one-dimensional scalar, and only use
> real functionality probes instead?

Indeed, that's what I suggested last time this topic came up. A linear
interface version number doesn't make much sense with a non-linear
development/deployment model...

Of course checking individual interface changes requires coming up with
a good autoconf test for the new interfaces. I hope Emilio already
started an extra thread on this...

Also, what to do with the existing interface version number? Update it
nevertheless for any new interfaces? Leave it there but don't ever
update it? Drop it alltogether?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]