Hi,
on one hand I'm happy to have stirred this discussion, on the other hand I don't want to abuse the ABCL mailing list, so if anyone is annoyed by this, please speak up!
I'm glad to see so much interest in the topic. I don't think time is ripe for a CDR, though. There are already two overlapping/competing features: hierarchical packages (in ACL and Pascal's implementation) and package-local nicknames (in SBCL, ABCL and...?) or pseudonyms, which are not hierarchical.
I'm exploring yet another route, that is, to conflate packages and symbols so that a symbol can serve as a namespace for other symbols; that naturally creates nice hierarchical structures, and the addition of a symbol alias operator in this context (which is necessary anyway to support global package nicknames) produces the availability of a limited sort of package-local nicknames. That route appears to be possible, at least in ABCL; a further research topic is to try in other Lisp implementations.
In addition to hierarchy and nicknames, this has the nice properties of:
1) making symbol/packages first class (packages are not in CL today, and I think they're the only data type with that property, am I mistaken?)
2) making packages naturally printable and readable with no special syntax (since they are really symbols)
3) reducing the number of types/concepts (although this is very debatable as packages won't disappear, since they're needed for backwards compatibility and compliance with the ANSI standard; their properties are simply transferred to symbols, making packages just a thin facade).
Recently, while I was in the middle of writing this, I discovered symbol-as-packages has drawbacks too - it doesn't play completely nice with existing Common Lisp as I hoped. But hey, exploration is good! :) That's why I've waited before sending this. Anyway, I think package-local nicknames or anything that builds upon packages and complicates them will most probably make the drawbacks of my approach bigger, and that's something I must take into account.
So, to make a long story short, I don't think the matter is settled yet. There's still space for exploration. From your answers, or rather from the absence of other answers, it seems like nobody is using these advanced package features at least on ABCL, which admittedly has a small user base. I'll try asking on the SBCL and ACL mailing lists.