Re: Plugin versioning?

[Brad <brad@comstyle.com>]

Well I guess you really havent taken a look over the ports tree. It mostly
comprises of patches that can not be contributed back because they would
be deemed as "local changes". There are exceptions to that but most of the
time they are out of our control.

// Brad

brad@comstyle.com
brad@openbsd.org

>> Versioning modules is a pain in the sphincter.  Apart from patching
>> the Makefiles, the code that does the loading needs to be fixed.
>> And since version schemes vary among unices, and I don't know of
>> a way to interface this with libtool, the resulting patches aren't
>> portable and can't be submitted back.
>
>I think a change this large is beyond the scope of the ports system.
>Having to patch a new application to implement this and update these for
>every release seems pointless, especially considering that these patches
>would probably never get incorporated back into the application.  One
>should not have to be forced to act as a developer of the application
>just to get it to build on an arbitrary platform.  This kind of
>modification seems suited to be handled by someone on the application's
>development team.