Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2016-05-15

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:47 ilbot3 joined #darcs
01:47 Topic for #darcs is now Darcs/Pijul Sprint, Helsinki, 6th-8th May http://darcs.net/Sprints/2016-05 | http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.10.3 is out http://darcs.net/Releases/2.10
05:09 Big_G joined #darcs
05:16 amgarchIn9 joined #darcs
09:50 stulli joined #darcs
12:52 mizu_no_oto joined #darcs
13:22 mizu_no_oto joined #darcs
14:08 Big_G joined #darcs
14:33 mizu_no_oto joined #darcs
15:25 roconnor_ joined #darcs
18:30 pbgc joined #darcs
19:36 pbgc joined #darcs
19:55 ilbot3 joined #darcs
19:55 Topic for #darcs is now Darcs/Pijul Sprint, Helsinki, 6th-8th May http://darcs.net/Sprints/2016-05 | http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.10.3 is out http://darcs.net/Releases/2.10
20:21 pbgc joined #darcs
20:28 mizu_no_oto joined #darcs
20:47 mizu_no_oto joined #darcs
21:05 fr33domlover Q: How do I get the details of the current revision of the working tree programatically? I want my program to display its revision, i.e. the darcs patch time and hash etc. from which it was built
21:05 fr33domlover (like the 'gitrev' package for for darcs')
21:06 fr33domlover Idea: Read the hashed_inventory file, parse the last patch in the file
21:06 fr33domlover will that correctly give me the info (minus the "dirty" state, i.e. whether unrecorded changes exist)
21:11 Heffalump look at the weak hash stuff that was recently released in darcs 2.12
21:11 byorgey fr33domlover: since darcs repos consist of a *set* of patches, it doesn't really make sense to look at the "last" patch
21:11 byorgey even if you look at e.g. the most recently recorded patch, that does not uniquely identify the state of the repo
21:16 fr33domlover byorgey, hmmm then how do I tell which patch is the last applied to the current working tree (assume there are no unrecorded changes)?
21:17 fr33domlover it doesn't have to be perfectly-mathematically-logically correct
21:17 fr33domlover just a way to display the revision of the software
21:19 fr33domlover Heffalump, isn't that a hash for the entire repo? i want to display a hash that i can use to determine which patches are included, or at least the last patch included
21:20 fr33domlover My workflow is: edit the code, `darcs record`, `darcs push`. So I make patches in a linear manner and I'd like the software to display info about the last change applied to it
21:21 fr33domlover Then people can tell roughly which version is running
21:24 byorgey fr33domlover: darcs log --last 1 will tell you the most recently recorded patch
21:26 byorgey it seems if you do  darcs log --last 1 --verbose, the first line is a hash
21:27 byorgey not sure if that's the best way to get it
21:40 fr33domlover byorgey, I already have code that parses the inventory and computes the hash
21:40 fr33domlover Should hopefully be the same as running `darcs` (I use my code to display repo change log in a web app)
21:50 Heffalump fr33domlover: I'm not clear what you want to use this revision for
21:52 Heffalump the weak hash is indeed for the entire repo, so you can compare it with another repo or some other hash you've seen before to know you've got the same repo state
21:53 fr33domlover Heffalump, suppose you run a dev version of your web app, e.g. because there are no stable releases or because you try new things on a dev instance
21:53 fr33domlover would be nice if the web app's page template says in the footer which version it is
21:54 fr33domlover i.e. hash/time/name of the last patch applied
21:54 fr33domlover so it's easy for people to know which code is running
21:54 fr33domlover which fixes are deployed, which aren't yet etc.
21:54 fr33domlover Heffalump, same use case as the 'gitrev' package
21:54 mizu_no_oto joined #darcs
21:54 fr33domlover I just want to make a Darcs equivalent
21:55 fr33domlover (and release it as a Hackage package of course)
21:57 Heffalump ok, if you really just want the last patch then you have a solution
21:57 Heffalump If you really want to linearize a repo/history, I would use tags rather than the "last patch".
21:58 dolio joined #darcs
21:58 Heffalump even if you make patches in a linear manner, they might get cherry-picked etc later
23:45 Riastradh joined #darcs

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary