Am Montag, 26. April 2010 15:13:24 schrieb Will Stephenson:
On Monday 26 April 2010 13:58:47 Adrian Schröter wrote:
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
If this is at all open to discussion, how will this appear in the clients?
Discussion happened before on opensuse-buildservice ml ;)
The term 'unresolvable' makes sense to me because I know about dependency resolution, but with my newbie head on I would understand it as 'unfixable error' and start doing random useless things to fix it like deleting and recreating the package.
yes, the state codes are never full understandable by itself. We still will need the legend beside with an explanation like in the past.
'Packages required for build not found' seems clearer to me. Perhaps this is too long to read well in a table, in which case 'reqtsnotfound' with a tooltip containing the longer text.
Yes, but this is no state anymore. Imaging how your monitor would look alike if every state would be this extensive -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org