On 02/ 4/10 05:27 PM, John Rice wrote:
What about allowing the user to do what they do now:
- Provide a name if they want to, assume its not the one known by the
publisher
- GUI catches the error, sees the name provided is not the known one, so
it then trys to add it again using the known name and sets up an alias
for the new publisher.
-- If the publisher has several known ones, pick the default if this is
possible.
-- If this fails again then you have an invalid repo origin and we would
need to flag that error to the user (may already catch this and report
it not sure).
- So normally the user has a nice easy experience they just add a
publisher, its aliased if necessary and all is well with the world.
No need for us to expose the above error and have the l10n issue.
Not quite true, there are a few scenarios in which you would still have
to error in some fashion:
* a publisher already exists with one of the 'known' prefixes
* a publisher already exists with an alias the same as one of the
'known' prefixes
* there's no publisher configuration information all (the repository is
misconfigured)
To be clear, I have no problem with making the 'known', 'unknown', and
'location' attributes accessible from the exception object itself. If
you want to put additional logic into place, that's the perogative of
the client. I'll do that tomorrow.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
