How will the API handle name collisions?
If user clicks on an .p5i file and the name specified is already in
use on the users system, what do we do, follow the BE approach and
add a numeric to the end of it? Will the API resolve this when it
does the authority/0 query against the depot server?
There are two different cases here:
1) update of existing authority
- as discussed previously, if an existing authority is found to have
the same origin_url as that in the .p5i file, it assumed to be the
same authority and some of its information will be updated with the
information from the .p5i file (such as the list of origin_urls,
mirror_urls, etc.)
Ok how is this update to be handled?
I assume we surface the udpates to the user by telling them the
authority information has changed (in an Update Authority dialog) and do
they want to update it? If so we need to know from the returned
Authority Info object that it has updates.
2) addition of new authority
- if the origin_url in the .p5i file doesn't match any existing
authority, but the name conflicts, the gui will handle this inherently
since it always prompts the user to add/update the repository while
the cli will simply fail letting the user know why it can't proceed
Yep that was the plan, I'd like to do what the Manage Repo dialog does
and if the Name for the New Authority is in conflict have a label in red
below the Name and URL fields indicating the problem to the user so they
can change it.
An origin_url is required in the .p5i file format and in the output of
authority/0 so this should be reasonable.
We intend to present an Add New Repo dialog to the user which will
have the Name field filled in but editable, to allow them to change
the name in such a case. Are we saying the user should not be able to
change the name?
Yes, they should not be able to change the name. Refer to Stephen's
original email on the proposed authority/0 operation [1].
I assume you mean user can't change the name of a registered authority
on the system, only when adding a new one.
JR
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
