[gmpi] Re: Reqs draft
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 10 Nov 2003 09:01:27 -0800
On Mon, Nov 10, 2003 at 09:36:00AM -0500, RonKuper@xxxxxxxxxxxx wrote:
> In terms of requirements, without going into implementation details, we need
> a registration system with the following attributes:
> - Avoids versioning conflicts, i.e., plugin version 2 overwrites version 1
> and projects which contain version 1 start blowing up.
Is this a requirement of the registration system, or just a best practice?
If developer wants Foo version 2 to supplant Foo version 1, and he names the
files the same and installs to the same place and overwrites v1, isn't that
his choice? And if it breaks -- his headache?
> - Avoids naming conflicts, i.e., 2 plugins by competing vendors called
> Reverb.DLL.
Fair enough!
> - Allows the user to organize and categorize to suit their needs.
Outside the host?
> - Supports "safe" and "friendly" diagnosis/uninstall/reinstall by users and
> support personnel.
What does this mean?
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
