If we use alternatives, presumably we'd set the deprecated version as higher priority. Sites would then need to change scripts or run a command to switch the alternative.
I think the key its that whatever we choose needs to be advertised well...and well in advance of delivering the new package. Thanks -Ben Peter Bonivart <[email protected]> wrote: On Thu, Sep 8, 2011 at 12:26 PM, Ben Walton <[email protected]> wrote: > If it will deliver working functionality (and the man page) I don't think it > should be named stub. > > So: alternatives, no alternatives but working functionality or stub with > deprecation notice binary? How about this: CSWpkgget/pkg_get: /opt/csw/bin/pkg-get -> deprecation notice /opt/csw/bin/pkg-get.deprecated -> the real pkg-get script Make the package depend on CSWpkgutil to go with the deprecation notice. This should make it almost painless for users, they will already have pkgutil on the system, they just have to start using it. And if they want to keep using pkg-get they can without jumping through hoops too much. The only problem would be if they are using pkg-get in some automated scripts, then alternatives would be safer. /peter _____________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
