I've been working on a package for storing arbitrary Go data structures as trees of Perkeep objects and reading them back out, and it's ready for some gentle early feedback. Please take a look at https://github.com/bobg/pk (godoc at https://godoc.org/github.com/bobg/pk).
You might remember the rich e-mail importer I wrote for Perkeep. It is now updated to work in terms of this new pk package. It's at https://github.com/bobg/pkmail. The cmd/pkmail subdir contains a command-line tool that can be used like this to import a folder full of e-mail messages: pkmail import FILE (where FILE is in a format understood by github.com/bobg/folder) and like this to reassemble a message from the tree of Perkeep blobs rooted at a given ref: pkmail get REF One question I have about the design of these packages is whether the links between blobs should be modeled using permanodes and attribute claims and so on. At the moment they are not. Going the full Perkeep-schema route seemed a little heavyweight for these tools, but perhaps the higher layers of Perkeep, with which I'm not too familiar (the indexer, the UI, etc), could interpret that schema info in a useful way if it existed? Cheers, - Bob -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/CAEf8c4-S5f8wTGyg7eyiNh9YFs0VF%2BBjggiuqZVZDSrov_XniQ%40mail.gmail.com.
