Re: [platform-update-dev] When to Update and when to Find New?

[Dorian Birsan <birsan@xxxxxxxxxx>]

Mark, there are no plans for a 3.1 fix,
but if you can provide a quality patch that won't introduce regressions
I think the eclipse team may accept it for 3.1.
I would personally go with solution
#1, provided it works. As long as your plugins have the correct dependencies,
you should be relatively fun. The user will need to know that all the features
must be selected.

-Dorian

"Your time is limited so don't let it be wasted living someone else's
life"   -- Steve Jobs

Mark_Melvin@xxxxxxxx
Sent by: platform-update-dev-bounces@xxxxxxxxxxx

06/16/2005 08:55 AM

Please respond to
"Eclipse Platform Update component developers list."

To	"Eclipse Platform Update component developers list." <platform-update-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-update-dev] When to Update and when to Find New?

Yes, this looks like the exact same
behaviour I was seeing.
 
So, what do you recommend as a workaround
for now?  I can see two things off the top of my head:
 
1) Adjust my match rules.
2) Always look for "new" features
to install.
 
While option 2 seems to work, it just
feels wrong to me.  It isn't a new feature - it is an update.  And
if I go with option 1, well then you can get into a state where you have
potentially incompatible features installed together.
 
Is there any plan to address this before
3.1 final?
 
Thanks for the pointer to the bug report.
Mark.
 
 
-----platform-update-dev-bounces@xxxxxxxxxxx
wrote: -----

To: "Eclipse Platform Update component
developers list." <platform-update-dev@xxxxxxxxxxx>
From: Dorian Birsan <birsan@xxxxxxxxxx>
Sent by: platform-update-dev-bounces@xxxxxxxxxxx
Date: 06/15/2005 09:49PM
Subject: Re: [platform-update-dev] When to Update and when to Find New?


This appears related to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=88464,
due to a limitation in the update searcher which accepts one feature at
a time, as they are found on the site. 

-Dorian 


"Your time is limited so don't let it be wasted living someone else's
life"   -- Steve Jobs

Mark_Melvin@xxxxxxxx
Sent by: platform-update-dev-bounces@xxxxxxxxxxx

06/15/2005 06:06 PM

Please respond to
"Eclipse Platform Update component developers list."

To	platform-update-dev@xxxxxxxxxxx
cc
Subject	[platform-update-dev] When to Update and when to Find New?

Hi All, 

We just released another internal milestone of our tools and I thought
I had the hang of this, but I am confused.  We have a few levels of
feature dependencies.  We released an update today, and I instructed
the users to go to Help > Software Updates > Find and Install...,
and choose to search for updates to current plugins.  The current
plugin set was 0.8.1, and we released 0.9.0 of everything today, so I also
instructed them to first change the "Valid Updates" setting in
the preferences to "compatible" so they could see the updates.
 Well, the problem was, the update procedure had to be done 4 times,
once for each level of feature dependencies.  So for example, if we
have Feature A, which requires Feature B, which requires Feature C (etc.),
the user could only first see the update to Feature C.  They then
had to restart, and look for updates again to now find Feature B, and then
do it all over again to find Feature A (now that they had upgraded their
other features). 
A particular user who didn't read my directions, simply blindly went and
looked for NEW features to install.  This happily gave him the option
to install version 0.9.0 of ALL of our features, and did the update mechanism
still did all the right things and disabled the old 0.8.1 versions that
were superceded with the "new" features.   

So, this just seems odd to me.  We released an update, not a new package.
 What I would *expect* to happen is for the update wizard to show
me ALL feature updates to 0.9.0, but not let me install v0.9.0 of Feature
A unless I *also* selected v0.9.0 of its dependencies.  Should it
not show me ALL available *updates* to all installed features, but still
do dependency checking on what I am installing (similar to the way the
install *new* features works)?  Is this a bug or am I doing something
wrong here?   

BTW - my match rule is "greater or equal" on all my dependencies,
but that shouldn't matter in my opinion.  The available updates wizard
should not restrict my choice to upgrade EVERYTHING, as long as I am upgrading
my dependencies at the same time. 

Thanks, 
Mark. _______________________________________________ 
platform-update-dev mailing list 
platform-update-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/platform-update-dev 

_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-update-dev
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-update-dev