https://github.com/creationix/gitfuse /var/lib/layman/my-overlay (R/O) /home/necrose99/my-overlay (LOCAL-RW) gitfuse remote. R/W anyhow it would be nice to configure a R/W copy of the overlay or specific overlays with git structures and option to have gitfuse for remote PUSH/Commit sync. layman's unionfs ?? or squash fs repoman FIX.... , repoman -commit > shove repo fixes/QA back to github etc.
ie layman -push-qa-fixes ie manifests
Not sure what you are suggesting us to do here. Complete sentences would help for a start.
got busy suddenly with calls. Basicly I want Layman to do the usual for an overlay /var/lib/layman.... however be able to define ie /home/$mydir/my-overlay git-clone /home/$mydir/my-overlay My working GIT(Hub/etc) copy Read/Write dont strip .git so one can git push overlayfs unionfs etc for fusion mounting , and or just making layman aware of local READ/WRITE copy. and some DIFF DB https://github.com/bcle/fuse4js https://github.com/creationix/gitfuse or the like to to make it easier to test changes to ebuilds , and thus push ie Manifest file changes back to github etc after a good test. git fuse looks interesting if it lets you mount the remote repo like a local folder for much the same and or can auto-push some fixes.
ie On a laymn pull it will pull a copy into a users home dir via git-clone as well as the standard var , if added Read/write. gentoo sunrise /home/necrose99/sunrise R/W and or symlink/s /var/lib/layman/sunrise or applicable. "foobar" now version 25 bump ebuild test copy ebuild to version 25 manifest/repoman the change , well all be it works/ or ahh cluster fzzz!@#$%^ (nuts try again) when working layman --send fix --changelog upstream package changed tested bump and works err something.... alias~y enter github USER/PASS PULL Request DONE. I've got the flu so I'm sweating bullets --so if I'm loopy forgive me. anyhow I was just hoping to bind laymans traditional repo , with ie my own R/W copy for tinkering, testing and fixing. ie in my home or /home/shared-repos/github I was just hoping to be able to point layman to r/w when testing , then point back to real repo when done.. or the like. push the fix and be done.
