Anybody? :( -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://refi64.com
On May 15, 2017 2:01 PM, "Ryan Gonzalez" <[email protected]> wrote: > Hello again! ;) > > > So, this is the LAST thing that's standing between Tup and Dart: > directory hardlinks. > > I'm not going to go into the use case right now, but here's a basic > example: > > > ryan@DevPC-LX ~ $ mkdir tup-links > ryan@DevPC-LX ~ $ cd tup-links/ > ryan@DevPC-LX ~/tup-links $ mkdir dir1 dir2 > ryan@DevPC-LX ~/tup-links $ echo 123 > dir1/x.in > ryan@DevPC-LX ~/tup-links $ cd dir2 > ryan@DevPC-LX ~/tup-links/dir2 $ ln -s ~/tup-links/dir1 dir1 > ryan@DevPC-LX ~/tup-links/dir2 $ howl Tupfile # This is just to > edit the Tupfile... > ryan@DevPC-LX ~/tup-links/dir2 $ cat Tupfile > : dir1/x.in |> cp %f %o |> x.out > ryan@DevPC-LX ~/tup-links/dir2 $ ls dir1 > x.in > ryan@DevPC-LX ~/tup-links/dir2 $ tup init > .tup repository initialized. > ryan@DevPC-LX ~/tup-links/dir2 $ tup > [ tup ] [0.121s] Scanning filesystem... > [ tup ] [0.254s] Reading in new environment variables... > [ tup ] [0.376s] Parsing Tupfiles... > * 1) [0.002s] . > tup error: Explicitly named file 'x.in' not found in subdir 'dir1' > tup error: Error parsing Tupfile line 1 > Line was: ': dir1/x.in |> cp %f %o |> x.out' > *** tup: 1 job failed. > [ ] 100% > ryan@DevPC-LX ~/tup-links/dir2 $ ls dir1 > x.in > ryan@DevPC-LX ~/tup-links/dir2 $ > > > I found this old mailing list post: > > https://groups.google.com/forum/#!topic/tup-users/4RJ3wv1x2SA > > and tried both updater.full_deps and ^c, but neither worked. Am I > missing something? > > -- > Ryan (ライアン) > Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else > http://refi64.com/ > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
