Third party Patch Manager

Eric Chatonet eric.chatonet at sosmartsoftware.com
Fri Jul 15 11:27:30 EDT 2005


Hi Alex,

Sounds good.
On the other hand, you are really mature to join the revInterop (Rev  
Interoperability) project :-)
http://groups.yahoo.com/group/revInterop

Le 15 juil. 05 à 17:20, Alex Tweedly a écrit :

> Eric Chatonet wrote:
>
>
>> Hi again Jim,
>>
>> I think the users and not the patches providers may ask runRev in   
>> order to obtain such a thing :-)
>> I think it would be useful for the community.
>> I think it would be courageous from runRev to accept it.
>>
>>
> If I was RunRev, I wouldn't be that courageous :-)  And, to be  
> honest, I'd rather that RunRev kept their efforts for the things  
> that we, the community, can't do ..... and organizing a list of  
> known patches is something we can do.
>
> I think we could satisfy the needs with a scheme like the following :
>
> Someone hosts a site that collects a list of known patches. (I'll  
> happily volunteer to do this,  it's about time I used some of my  
> web space for something useful - though in some ways it would be  
> better if it were hosted by one of the already well-known sites  
> like Ken or Richard (or revJournal ??))
>
> The list consists of, for each patch,
> author, date, URL for the patch, description, version it was  
> written for, Bugzilla number, fixed-in version
>
> Note the most important part of that is the Bugzilla number -  
> either of a bug report or enhancement request. This ensures that  
> RunRev are aware of the need (desire) for a change, and provides a  
> reliable mechanism to verify whether the feature (or fix) has been  
> incorporated into a later release.  The "fixed-in version" can be  
> filled in later, based on the changes in the BZ database when a new  
> release comes out.
>
> The list of patches could be accessed via web browser, or via a  
> small stack (again, I'll write this if there is interest .... but I  
> won't be doing that until mid-August onwards). The stack would pick  
> up any updates from the URL, allow the user to mark which patches  
> she has applied to which version on which machines, etc.
>
> So at any time you could go run this stack, and determine if there  
> are patches you'll need to apply to a new version, or whether there  
> are new patches.
>
> The quality of the patches would be entirely up to the author of  
> any patch - no judgment to be applied by the list-holder.
>
> The patches remain on the author's own web-site - and hence can be  
> withdrawn, updated, or otherwise changed. Optionally, they could  
> also be uploaded to the patch-list site, e.g. if the author didn't  
> have web space available.

Best Regards from Paris,

Eric Chatonet.
----------------------------------------------------------------
So Smart Software

For institutions, companies and associations
Built-to-order applications: management, multimedia, internet, etc.
Windows, Mac OS and Linux... With the French touch

Free plugins and tutorials on my website
----------------------------------------------------------------
Web site        http://www.sosmartsoftware.com/
Email        eric.chatonet at sosmartsoftware.com/
Phone        33 (0)1 43 31 77 62
Mobile        33 (0)6 20 74 50 86
----------------------------------------------------------------




More information about the use-livecode mailing list