[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]
RE: st: Which and return list
> I guess the flaw with the upstream solution is that this
> requires the users of your programs to be as efficient as you
Not so; -profile.do- is implemented automatically.
Once people have the right -profile.do- the problem
is on Fred's side.
> I get many emails like "why can't your program do this?" and
> generally the solution is have you done this command -ssc install
> This is ok for new features of old commands (that are already
> but when you create a new command that
> requires a newer version of an old command should I
> automatically force
> every user to update the commands I want updated? This would
> be the easiest way for me and would
> be an upstream solution but I doubt the person sitting on a
> slow phone line will thank me.
I am not clear who your users are here, i.e. whether this
is an in-house issue, or you are supporting people
out there interested in your programs.
There would seem to be at least two solutions:
1. Your users sound ungrateful and unreasonable.
At some point they should be invited to re-examine
their assumptions about what support you can provide.
For example, they could copy your programs and implement
the features they want themselves.
2. If your main program requires others, wire
those others in as subroutines; or set up the
main and others as a package so that installing
one installs the lot.
* For searches and help try: