<mark_weaver>youlysses: I'm not sure about multiple licenses, but I see that some packages do something like this: (license (list gpl3+ bsd-4 public-domain)), e.g. 'util-linux' in linux.scm.
<mark_weaver>youlysses: however, I think that means that some files are covered by gplv3-or-later, other files are covered by bsd-4, and others are in the public domain. I'm not sure how to represent dual-licensing. It's a question for one of the more experienced Guix devs.
<youlysses>mark_weaver: Any idea why the offical packages are just marked as GPLv2 currently, then?
<youlysses>mark_weaver: I think I need to throw in g++, and maybe more for libtorrent -- that being said... yeah, dang it. :^)
<mark_weaver>youlysses: well, you probably don't need g++. I think that's considered an input by default.
<mark_weaver>anyway, the build daemon does the building in the chroot where only the inputs are available, so if something's missing, you'll notice it because it won't build (or it will be missing features in the case of an optional dependency)
<mark_weaver>youlysses: according to the Debian copyright file, the license is GPLv2-or-later, not GPLv2
<mark_weaver>which means I guess you want (license gpl2+), not (license gpl2)
<mark_weaver>well, "guix package" does fairly arbitrary atomic changes to your profile, and that can be more than just installs.. you could install some things, remove some things, upgrade some things, etc. all in one atomic operation.
<mark_weaver>so it can't simply be -i and then everything after that is a package name.
<youlysses>I'll have a general list of "Greviences and Concerns" that I'll submit, probably next weekend. :^P
<mark_weaver>fair enough :) Guix is still a young project, and rough around the edges.
<youlysses>mark_weaver: Coming from vast amounts of inexperience in this realm (packaging and even to a large degree scheme) it certainly does seems rough in some areas, but I'm very hopeful and too hopefully will be running Guix fullitme and contributing on a regular basis soon after. :^)
<mark_weaver>yeah, I'm very excited about the potential of Guix. I intend to switch all of my machines to it almost as soon as its bootable.
<youlysses> So, pulled and in my ~/gnu/packages/ and I copied my rtorrent.scm into said directory -- ran "GUILE_LOAD_PATH=~/gnu/packages/ guix build rtorrent ... and nothing. :^U
<mark_weaver>there are ways you could load that file anyway, and use it to build the package, but the easy integrated things like 'guix package -i' and 'guix build' only look in the (gnu packages *) modules for packages.
<youlysses>Also, yeah -- I was planning on doing so this/last weekend, but I ended up having to go home to my parents to deal with a minor "family emergency"... that being said, I think I'll have some time this coming weekend to finally watch it. :^)
<mark_weaver>youlysses: oh well, sorry to apparently be clueless about this. Like I said, I've only contributed a little bit to Guix and my method of operating is different.
<youlysses>mark_weaver: Really, no problem -- it's just a stronger motivation to get a lot more in-depth to/around the system in the weeks/months to come. :^)