[tex-hyphen] pattern packaging

[Karl Berry]

    > Anyway, please create a draft and I'll comment.  It's easier to refine
    > a real instantation than figure it all out in a void.
    Done. 

Thank you very much.  It looks good overall.

My one thought is that it would simplify things for me if
tex/generic/config was not in the hyph-utf8 TDS package.  The filename
doesn't fit.  

Seeing it now, I do appreciate your generating it.  However, I can
simply import it directly from your repo to TL; I don't see that it buys
anything much to have it on CTAN.  (Unless MiKTeX can make use of it,
which I do not know.)

In general, everything in the TDS version should be under hyph-utf8/ subdirs.

    If one chooses to install hyphen-slovenian, then the old file
    doesn't need to be installed. But under what condition would the old
    file be installed then?

Maybe it doesn't need to be, but I am thinking that it will be.  

    Is there a need for something like hyphen-legacy.tlpsrc package
    where all the old files would be listed?

I am thinking the other way around, actually:
- existing packages and patterns stay as they are, at least this year.
- you upload hyph-utf8 to CTAN.
- I import hyph-utf8 to TL.
- the hyph-utf8 package will include all your files, and always be
  installed.

This seems like the simplest thing to do in terms of maintenance.  The
files are so small that it doesn't seem worth splitting them up into
different packages to me.  It would be a time-consuming hassle to do that.
(For the same reason, we always installed all xu-* files last year.)

    But maybe I'll call the top level TDS instead of hyph-utf8.

If you want.  In the repo, it doesn't matter.  When you upload to CTAN,
there should be no top-level directory name at all in the TDS-ready
CTAN:install/...tds.zip file.  It should just unpack with top-level
directories tex/ and source/.

karl