<g_bor[m]>I'm having a look at a possibility of a maven build system.
<g_bor[m]>ISTM it would be useful to have the pom.xml-s included in our jar files, if it exists in the source, as we could avoid specifiying maven coordinates in our package definitions, if those really match to the coordinates of the source we use. As far as I can see we still need a way to add the maven coordinates, as we sometime use different version than the dependency listed, to avoid version bloat. WDYT?
<g_bor>civodul: It goes like this: there's a file to list the dependencies, each dep has a name and version. These names and versions are specified in the build tree. If we have a package that needs a dependency, then if we have exactly that version, and have this information embedded into the artifact, then we don't need to specify these. However, currently it seems that we have to fake version information to avoid
<demotri>g_bor[m]: OK. I see. First, I think: Yes, we should add the pom.xml into jar:META-INF/pom.xml folder. Further, we should place the pom.xml along with the jar (like it is the case in ~/.m2/repository).
<demotri>g_bor[m]: Maybe it would be even good to place the jar+xml in the store like we have in mvn repo: /gnu/store/...-package/org/my-company/my-project/1.2.3/my-project-1.2.3.jar
<demotri>g_bor[m]: Adding the pom.xml into the jar is something that mvn already does (when we finally build with maven).
<demotri>g_bor[m]: Why do you think we need the mvn coordinates (groupid:artifactid:version) in the package definition?
<demotri>g_bor[m]: Would it be an idea to name the packages like the coordinates? maven-org.my-company:my-cool-project
<rekado_>I’d prefer to specify this as a property in the package definition.
<rekado_>jars can be built with ther build systems, so I wouldn’t like to name them after the conventions of just one build system.
<g_bor>I intend to use the maven-install plugin to create a local repository. It can infer the maven coordinates, if the pom.xml is in the jar file. In that case we don't need to add these to the package definitions.
<rekado_>sneek: later tell pkill9 You don’t need to add a module to the kernel source. It can be a separate package. You just need to add it to the list of kernel modules in the operating-system configuration.
<sneek>pkill9, rekado_ says: You don’t need to add a module to the kernel source. It can be a separate package. You just need to add it to the list of kernel modules in the operating-system configuration.
<thomassgn>wigust: for some reason, the printing works today. I have rebooted once between. Now I just have to figure out why the printer with ink prints blank pages. Was watching the logs but they don't give me anything on the color issue... :P Thanks for the help
<g_bor[m]>clojure fails on master, on phase 'create-jar-indices with "is a directory". Is it safe to delete this phase, or should I adjust it?
<g_bor[m]>roptat: unfortunately not yet. rekado tried it several way, no success yet. I asked if it would be acceptable to finish the bootstrap path like build a 32 bit ghc and cross-compile a 64 bit one from that, but he said he would like to get rid of nhc, and compile a patched a patched ghc instead.
<OriansJ>jlicht: our issue with Rust is when they introduce new features, they have a bad habit of requiring them to build the new version with them. But as a developing community, we hope they will mature out of that soon.
<nixd>How would one go about creating a new package? I keep reading that the package definition has to be "in place"/in the guix source tree. Say, you have a package definition in a thepackage.scm file somewhere in ~/, and I want to try if it works. How would one proceed?
<pkill9>nixd: you can specify additional directories of package definitions by adding them on the ocmmand-line with -L, or adding them to the GUIX_PACKAGE_PATH environment variable
<nixd>pkill9 Is it normal that there is no GUIX_PACKAGE_PATH env variable by default?
<nixd>I don't see one when running printenv anyways.
<nixd>When I try guix build -L /the/path -K --verbosity=5 I merely get "building (newline) | entered goal loop". Without the verbosity flag I don't get any return value. What am I doing wrong?
<pkill9>i have it set in my ~/.profile so everytime i run the guix command, it will include my personal 'repository'
<nixd>pkill9 Thanks. I've now also tried guix build with -L and the directory, but I don't get any output from guix build at all. With verbosity=5 I just get "building" and "entered goal loop". Not sure whats wrong
<pkill9>nixd: can you post your package definition into a pastebin?
<nixd>pkill9 I will do that tomorrow. Ill see if I can find time to post it when you're here aswell. Thanks for now!
<aminb>hi all, anyone know why guixsd still doesn't support lvm?
<g_bor[m]>aminb: it seems there was actually nobody really interested in implementing it. Last time I investigated this I noticed that lvm very badly maps to the current mapped device concept. Furthermore there seems to be a problem regarding including stuff in initrd, if I am correct now we generate an initrd with 'everything needed'. luks in itself can be used however.
<kballou>aminb: static compilation for lvm seems to have been problematic so far... I wanted to look into this because I'm also interested in getting LVM support, but I'm still trying to get my feet wet :/
<kballou>g_bor[m]: would `uuid` mapping work for lvm partitions if static compilation was working?
<g_bor[m]>I am also interested, and I have seen some work regarding the static compilation on the mailing list.
<g_bor[m]>Actually I would like to use the classic vgchange -a y as a mapped device activation, but a volume group is a bad mapped deviceish thing, as it not really a source, nor a target.