Al J <allen.jos...@gmail.com> writes: > > > I’m building 3 deliverable versions of kiosk software from one repo, and I > foresee a PITA coming down the road at me > > > I've got base classes in a common area and subclasses with the differences > > > Right now I’m using a symlink, repointed with an npm script -- it works > because I can choose which product to run/build/test & package > > > product -> products/productB > > products: > > base-class > > productA: > sub-class (from ../base-class) > > productB: > sub-class (from ../base-class) > > productC: > sub-class (from ../base-class) > > Is this an ok way to proceed? > > > I don't want to use branches because I can't deal with push/stash checkout > pop/unstash (whatever) > > > I read about worktrees - but I think they are for the whole repo ?
I suspect this is entirely language / build-system dependant... because, well, I don't ever run into this problem in the languages I use ;) (C/C++ with CMake, Haskell with stack, Clojure/ClojureScript with lein, ...) So my suggestion would be that you approach a group related to npm (I'm guessing this is JavaScript then, right?) /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Where the people fear the government you have tyranny. Where the government fears the people you have liberty. — John Basil Barnhill -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
