<mark_weaver>take a look at gnu/packages/texinfo.scm, for example. I recently added version 4.13a because it's much faster than 5.2, and my machine is slow.
<mark_weaver>also, if the package is already in your store, you can install it in your profile by passing the absolute store directory name as an argument to "guix package -i", although that's a bit hacky and has some disadvantages.
<rgc>The thing is that I see use cases for development, when there's a dependency on an old version. I need lua 5.1 for example ...
<rgc>nono, it's that I need it. It's a project I work on
<mark_weaver>well, if you need it, then maybe others in a similar situation need it too. is it just for testing purposes? can you help me understand?
<rgc>well, there are some differences in lua 5.1 and lua 5.2 that make that some libraries work just in one or the other.
<mark_weaver>but in any case, if you need local packages that you think won't be of interest to others, or any modifications to guix that you prefer, the best way I know is to create a local git branch of guix, and use that. git makes it easy to merge the upstream changes into your local branch.
<mark_weaver>rgc: well, it sounds like we should add lua 5.1 then.
<mark_weaver>civodul: regarding building 'shadow' from git, I was thinking of making a separate package the builds the tarball using 'make dist', and then using that as the 'source' for the existing 'shadow' package. does that make sense? I'm reluctant to muck up the 'shadow' package definition itself, especially since the tarballs might become available again at some point.
<mark_weaver>btw, I recently learned that bitlbee now supports the latest libotr, but they haven't bothered to cut a new release. I got on IRC with them and tried to convince them to release, but they don't seem to care much. Debian has a package based on a later revision from their subversion repo that they recommend to all users who aren't building from source :-/