[EMAIL PROTECTED] wrote:
>> Where can I find documentation, on what these IPS "actions" are?
>
> Pull a clone of the the pkg gate. The actions are in
> src/modules/actions
That's not "documentation".
Are you saying that all these wonderful "will solve everything" components,
have neither an explicitly written design specification, nor documentation?
How do you expect people outside sun to fairly use, and give feedback, on
these tools, if you have zero documentation besides, "use the source"?
How do you expect people to be able to understand how IPS actions solve a
somehow "unsolvable" problem, if you dont even document how they work?
Or do you not actually want people to understand anything, but just go along
with, "trust us, we know what's good for you better than you do" ?
The latter approach is really, really bad customer interfacing. And it has
failed rather spectacularly for Sun in the past, on multiple occasions.
>> You complain, "people dont do it right", but you don't show them HOW
>> to "do it right" !!
>
> You're making a duplicitous argument. You accuse Sun of being
> incompetent and unable to use their own tools. If you honestly believed
> that, how could you possibly argue that Sun should also be showing
> people how to use these tools that you allege they don't or can't
> properly use?
Sun is a large organization. To make a claim that ALL of sun is [anything],
would be foolhardy.
(if i thought that Sun was incompetant through it's entire organization, I
would choose to no longer use sun products)
I make the claims that
- At least some of the team(s) involved in creating patches, arent doing it
right
= This creates "problems with patching", that are solvable problems, if
the sun process and approach to patching was re-engineered.
= To re-engineer the process, does not require throwing away the existing
tools and writing replacement ones. Only extentions to existing ones.
- Sun is choosing to avoid the problem(s), rather than fix it.
Your own statements, adds credence to the second statement of mine.
You explicitly state that this radical course is not REQUIRED, but only a
"choice", by people who have chosen to work on the "new and shiney" IPS,
rather than less glamorous "fix the old stuff" work.
Specifically, below:
> This isn't a matter of could not be done. Rather, as a consequence of
> the other design goals that we've chosen for IPS, this shall not be
> done.
In other words, "we're not going to fix the old stuff, because we want to
force people to use the new stuff instead. not because it's unfixable".
--------------------
> As Bart has repeatedly stated: We're changing the tools so that they may
> only be used correctly. This means that even if Sun is as incompetent
> as you claim, we'll be able to cleanly generate packages and get
> updates to our customers properly. This sounds like something that even
> you could agree with.
>
There is no such thing as an idiot-proof tool.
"Make it idiot-proof, and someone will make a better idiot. "
However, in your attempts to do the impossible, you are also trying to
eliminate features that I, and others find very useful, if not indispensible.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
