old school repo

gistfile1.txt

For simple modules like PP, no "resources":
- module provides list of dependencies that can be checked by simply perl6 -MDep:Endency -e ''
- module provides author and version 
- $ github clone module
- $ cd module
- $ ufo install /usr/lib/perl6  # cp -r lib/* /usr/lib/perl6/module/name/author/version  # or into private repo dir
- $ cd /usr/lib/perl6; git status; git add *; git commit  # optional
- file hashes (ftp-server style) can be used/generated/provided by module/ufo/admin
- /usr/lib/perl6/* don't have precompiled files, that is v6-compiler business somewhere else, \
     so /usr/lib/perl6 is Perl6 code dir for all implementations, as provided by author
- post install/cp: $ ufo precompile /usr/lib/perl6/module/name/author/version
- whole /usr/lib/perl6/ can be tar.gzipped (excluding .git/)
- no damn HASHEFILES ANYWHERE!!!1 in that type of repo
- such repo point is: it is managed by admin (or equivalent) in seqential way, can be locked (for write), \
     no sudden code changes - write once per version
- every compiler keeps precompilations for all combinations of versions he wants :>  but somewhere else ! or \
    just for latest versions... :)
- resources can go to /u/share/p6/m/n/a/v  # problem with usrLibPerl6.tgz: /u/l/p6/m/n/a/v/[code|rsc|doc] ?