[EMAIL PROTECTED] wrote:
Do we have a customer use case where a per-authority UUID is okay, but a
per-image UUID isn't?
I'll need to have Stephen chime in on this one. I was under the
impression that when he said "Because it allows correlations between
repositories that some sites might find unacceptable." that this was
based on real customer use cases.
One of the comments that Stephen supplied in this thread was that the
UUID should be opt-out, not opt-in.
I'm expecting that this will be handled by an installer. A UUID cannot
be set for a pre-installed image that is copied from a CD or downloaded
because then everyone would have the same one. So it has to be set by
the installer (by calling --reset-uuid). That part will be automatic,
and to opt out, someone can run --unset-uuid.
I agree that the user interface would be simpler if this was not
per-authority.
Tom
begin:vcard
fn:Tom Mueller
n:Mueller;Tom
org:Sun Microsystems, Inc.;Update Center Software
adr:;;21915 Hillandale Dr;Elkhorn;NE;68022;USA
email;internet:[EMAIL PROTECTED]
title:Senior Staff Engineer
tel;work:877-250-4011
tel;fax:877-250-4011
tel;home:402-916-9943
x-mozilla-html:TRUE
version:2.1
end:vcard
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
