pcp
[Top] [All Lists]

Re: Preparing 2.6.0 release

To: Max Matveev <makc@xxxxxxx>
Subject: Re: Preparing 2.6.0 release
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 29 Jun 2006 21:40:59 +1000
Cc: pcp@xxxxxxxxxxx
In-reply-to: <17571.31606.336086.997238@xxxxxxxxxxxxxxxxxxxxxx>
Organization: Recreational Computing Nirvana
References: <17571.31606.336086.997238@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: kenj@xxxxxxxxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Thu, 2006-06-29 at 17:04 +1000, Max Matveev wrote:
> I'm getting ready to release pcp 2.6.0. Current snapshot in available
> as 2.5.99 from ftp://oss.sgi.com/projects/pcp/download/dev.
> 
> Here is the list of changes since 2.5.0 - numbers are SGI Bugworks
> numbers and provided for reference purposes only:
> 
>     - 947510 - don't try to write into the string returned by strerror
>     - 947781 - add functions to implement asynchornous communication
>                with pmcd and functions to implement application main loop

Was there any discussion on the list about this?

- rationale?
- compatibility issues?
- no apparent changes to pmproxy ... was the asynchronous stuff ever
tested with pmproxy ... on the face of it I don't see how it could
possibly work which leaves at least one person stuck ... 8^(>
- why is libpcp.so.2 a symlink to libpcp.so.3 when the ABI has changed
so radically?  For those of us not using IRIX, how is backwards
compatibility supposed to be maintained, e.g. newly linked apps cannot
run on old pcp installations

Other than that

a. it complies and installs fine on Fedora Core 4 (I'll try Windows
tomorrow)

b. I have a bunch of other patches that I'll have to redo against
2.5.99 ... can you hold off until I can do that, or do you just want to
wait and get a dumping of day-1 patches for 2.6 when it releases?


<Prev in Thread] Current Thread [Next in Thread>