On Sat, Jun 25, 2011 at 21:47, Kent Fredric <kentfredric@...> wrote:
> Package names themselves can be thusly arbitrary , and could be a SHA
> sum or something obscure, as long as all internals and dependencies
> used the same arbitrary name, things would work as intended.
>
I mentioned this idea of internally referencing packages by a hash in
the other thread.  As long as we're clear that the most common
operation (emerge -av ${PN}) is still exposed to the user, it's
perfectly valid.  I want to be very sure we're clear in our
understanding that tags are for discovery in cases where the user is
not sure what is available (like categories).

As for the latter part, the size of a git repo becoming umanageable
over time had not occurred to me, I'm afraid-- would it work to use
shallow clones?  Otherwise, the herd-wise division is probably
acceptable.  Need to think about that one more.

Regards,
Wyatt