On Fri, 14 Jul 2017, D'Arcy Cain wrote:
On 07/14/2017 05:07 AM, Stephen Borrill wrote:
On Thu, 13 Jul 2017, D'Arcy Cain wrote:
If it's strictly local why bother? Just "make replace" or remove the package before rebuilding. PKGREVISION is meant for causing rebuilds when the user doesn't realize that a change has been made e.g. when running pkg_rolling-replace.
By local I mean not committed to pkgsrc. The built packages are used by customers' machines, so the change needs to be noticed by them.
Yes, I understood that. And now I understand the child server requirement. I just wonder if making local mods in a CVS tree as a matter of course is the cleanest method. Of course I don't know your actual situation so I can't really say. From this discussion it sounds like you regularly need to modify packages after they have been installed elsewhere and that it happens often enough (or you have too many child servers) to be able to handle each change manually.
What kind of modifications are you making that don't warrant an update to pkgsrc itself?
It could just be changing the options the package was built with.
--
Stephen