diff options
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 30 |
1 files changed, 30 insertions, 0 deletions
@@ -133,6 +133,12 @@ longer needed at all? easily overtake upstream texlive) Question: Do we need the source part at all? Isn't it irrelevant? + Maybe first we go WITHOUT the source: part until we know how it will + be handled. THere is the option to set the source in some different way + via some configuration tlpdb. + + See below that we don't need the whole source part at all ... + - multi-source support I think all that ideas with pinning etc are overkill, since we will not have that many different sources. I propose that we use only revision @@ -150,6 +156,30 @@ longer needed at all? (needs generalize revision patch) + Current ideas: + - in the tlpdb add some short name to a source + depend location:http://mirror.ctan.org/.... ctan + depend location:http://local.server.foo/... department + and then call + tlmgr install package/ctan (installs from ctan source) + tlmgr install package/department (installs from department) + tlmgr install package (installs the highest rev number) + + - add a config file + package:source:pin + default pin is 100, higher is stronger .. + if "package" should be installed or upgraded, the following check is done + . take a look at all candidates and compute the pins of them + (default is 100) + . promote those with the highest pin (can be only one, or all) to the + new set of candidates + . within the new set of candidates choose the highest revision number + + That would allow: + . packages can be pinned to a specific source, and will not be updated + even if another source ships a higher version number + . ??? + - (Master/tlpkg/etc/installed_avail_archs.diff) currently there is a mess-up wrt to available and installed architectures. We use 00texlive-installation/available_architectures for both the set |