Re: [Nix-dev] Proposed feature for make-wrapper.sh
Thanks for your feedback. I just edited the wrapper in postInstall. Inspired by Mr. Qiu, it's in PR 15421 which is about a week old without any interaction. On Sunday, May 08, 2016 12:39:20 PM Domen Kožar wrote: > I wanted that feature a few times also, but I ended up using --run or two > wrappers. > > On Sun, May 8, 2016 at 12:32 PM, Wout Mertens > > wrote: > > --suffix-flags sounds ok, but perhaps a custom wrapper is better. > > > > On Sun, May 8, 2016, 11:02 AM Philip Carlsen wrote: > >> That's great to hear - Indeed you're not the only one having trouble with > >> akonadi. I just gave up before I could make anything useful of it. > >> > >> Den 8. maj 2016 01.24 skrev "Phil Wetzel" : > >>> Greetings, > >>> > >>> I've just installed NixOS on my desktop with KDE. I had trouble getting > >>> akonadi working (the data backend for kdepim). I found one other person > >>> with > >>> the same problem [1], though it is hard for me to believe I am the only > >>> person > >>> trying to run KMail on NixOS. > >>> > >>> The problem turned out to be akonadi starting an instance of mysqld > >>> (mariadb) > >>> that failed to find an error messages file because it didn't know where > >>> it was. > >>> Setting the --basedir prevents this problem from occurring, and that is > >>> what > >>> is done in the service module definition. kdepim users can solve the > >>> problem > >>> locally by setting basedir in their akonadi/mysql.cf config, but if we > >>> would > >>> like it to work out of the box it seemed to me that the way forward was > >>> to use > >>> wrapProgram on mysqld. You can't actually run mysqld from the > >>> commandline > >>> without without the --basedir argument with it packaged the way it is > >>> now > >>> anyway. > >>> > >>> This turned out to not work either because: > >>> - wrapProgram --add-flags *prepends* all the wrapped flags to the > >>> > >>> argument list > >>> > >>> - akonadi uses the --defaults-file argument > >>> - mysqld requires --defaults-file to be the first argument if it is > >>> used > >>> > >>> This can certainly be solved with some hackery after the wrapProgram in > >>> postInstall, but perhaps it would be better to include a --suffix-flags > >>> feature > >>> to make-wrapper.sh. > >>> > >>> What would you suggest as the better choice? I didn't want to submit a > >>> PR with > >>> a hack if that wasn't the way forward, and I definitely didn't want to > >>> submit a > >>> PR touching the build tools and documentation without at least saying > >>> hello > >>> first. > >>> > >>> Thank you, > >>> Phil Wetzel > >>> > >>> [1] - > >>> http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015575.html > >>> ___ > >>> nix-dev mailing list > >>> nix-dev@lists.science.uu.nl > >>> http://lists.science.uu.nl/mailman/listinfo/nix-dev > >> > >> ___ > >> nix-dev mailing list > >> nix-dev@lists.science.uu.nl > >> http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > > -- > > > > Wout. > > (typed on mobile, excuse terseness) > > > > ___ > > nix-dev mailing list > > nix-dev@lists.science.uu.nl > > http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Proposed feature for make-wrapper.sh
I wanted that feature a few times also, but I ended up using --run or two wrappers. On Sun, May 8, 2016 at 12:32 PM, Wout Mertens wrote: > --suffix-flags sounds ok, but perhaps a custom wrapper is better. > > On Sun, May 8, 2016, 11:02 AM Philip Carlsen wrote: > >> That's great to hear - Indeed you're not the only one having trouble with >> akonadi. I just gave up before I could make anything useful of it. >> Den 8. maj 2016 01.24 skrev "Phil Wetzel" : >> >>> Greetings, >>> >>> I've just installed NixOS on my desktop with KDE. I had trouble getting >>> akonadi working (the data backend for kdepim). I found one other person >>> with >>> the same problem [1], though it is hard for me to believe I am the only >>> person >>> trying to run KMail on NixOS. >>> >>> The problem turned out to be akonadi starting an instance of mysqld >>> (mariadb) >>> that failed to find an error messages file because it didn't know where >>> it was. >>> Setting the --basedir prevents this problem from occurring, and that is >>> what >>> is done in the service module definition. kdepim users can solve the >>> problem >>> locally by setting basedir in their akonadi/mysql.cf config, but if we >>> would >>> like it to work out of the box it seemed to me that the way forward was >>> to use >>> wrapProgram on mysqld. You can't actually run mysqld from the commandline >>> without without the --basedir argument with it packaged the way it is now >>> anyway. >>> >>> This turned out to not work either because: >>> >>> - wrapProgram --add-flags *prepends* all the wrapped flags to the >>> argument list >>> - akonadi uses the --defaults-file argument >>> - mysqld requires --defaults-file to be the first argument if it is used >>> >>> This can certainly be solved with some hackery after the wrapProgram in >>> postInstall, but perhaps it would be better to include a --suffix-flags >>> feature >>> to make-wrapper.sh. >>> >>> What would you suggest as the better choice? I didn't want to submit a >>> PR with >>> a hack if that wasn't the way forward, and I definitely didn't want to >>> submit a >>> PR touching the build tools and documentation without at least saying >>> hello >>> first. >>> >>> Thank you, >>> Phil Wetzel >>> >>> [1] - >>> http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015575.html >>> ___ >>> nix-dev mailing list >>> nix-dev@lists.science.uu.nl >>> http://lists.science.uu.nl/mailman/listinfo/nix-dev >>> >> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > -- > > Wout. > (typed on mobile, excuse terseness) > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Proposed feature for make-wrapper.sh
--suffix-flags sounds ok, but perhaps a custom wrapper is better. On Sun, May 8, 2016, 11:02 AM Philip Carlsen wrote: > That's great to hear - Indeed you're not the only one having trouble with > akonadi. I just gave up before I could make anything useful of it. > Den 8. maj 2016 01.24 skrev "Phil Wetzel" : > >> Greetings, >> >> I've just installed NixOS on my desktop with KDE. I had trouble getting >> akonadi working (the data backend for kdepim). I found one other person >> with >> the same problem [1], though it is hard for me to believe I am the only >> person >> trying to run KMail on NixOS. >> >> The problem turned out to be akonadi starting an instance of mysqld >> (mariadb) >> that failed to find an error messages file because it didn't know where >> it was. >> Setting the --basedir prevents this problem from occurring, and that is >> what >> is done in the service module definition. kdepim users can solve the >> problem >> locally by setting basedir in their akonadi/mysql.cf config, but if we >> would >> like it to work out of the box it seemed to me that the way forward was >> to use >> wrapProgram on mysqld. You can't actually run mysqld from the commandline >> without without the --basedir argument with it packaged the way it is now >> anyway. >> >> This turned out to not work either because: >> >> - wrapProgram --add-flags *prepends* all the wrapped flags to the >> argument list >> - akonadi uses the --defaults-file argument >> - mysqld requires --defaults-file to be the first argument if it is used >> >> This can certainly be solved with some hackery after the wrapProgram in >> postInstall, but perhaps it would be better to include a --suffix-flags >> feature >> to make-wrapper.sh. >> >> What would you suggest as the better choice? I didn't want to submit a PR >> with >> a hack if that wasn't the way forward, and I definitely didn't want to >> submit a >> PR touching the build tools and documentation without at least saying >> hello >> first. >> >> Thank you, >> Phil Wetzel >> >> [1] - >> http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015575.html >> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > -- Wout. (typed on mobile, excuse terseness) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Proposed feature for make-wrapper.sh
That's great to hear - Indeed you're not the only one having trouble with akonadi. I just gave up before I could make anything useful of it. Den 8. maj 2016 01.24 skrev "Phil Wetzel" : > Greetings, > > I've just installed NixOS on my desktop with KDE. I had trouble getting > akonadi working (the data backend for kdepim). I found one other person > with > the same problem [1], though it is hard for me to believe I am the only > person > trying to run KMail on NixOS. > > The problem turned out to be akonadi starting an instance of mysqld > (mariadb) > that failed to find an error messages file because it didn't know where it > was. > Setting the --basedir prevents this problem from occurring, and that is > what > is done in the service module definition. kdepim users can solve the > problem > locally by setting basedir in their akonadi/mysql.cf config, but if we > would > like it to work out of the box it seemed to me that the way forward was to > use > wrapProgram on mysqld. You can't actually run mysqld from the commandline > without without the --basedir argument with it packaged the way it is now > anyway. > > This turned out to not work either because: > > - wrapProgram --add-flags *prepends* all the wrapped flags to the > argument list > - akonadi uses the --defaults-file argument > - mysqld requires --defaults-file to be the first argument if it is used > > This can certainly be solved with some hackery after the wrapProgram in > postInstall, but perhaps it would be better to include a --suffix-flags > feature > to make-wrapper.sh. > > What would you suggest as the better choice? I didn't want to submit a PR > with > a hack if that wasn't the way forward, and I definitely didn't want to > submit a > PR touching the build tools and documentation without at least saying hello > first. > > Thank you, > Phil Wetzel > > [1] - > http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015575.html > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Proposed feature for make-wrapper.sh
Greetings, I've just installed NixOS on my desktop with KDE. I had trouble getting akonadi working (the data backend for kdepim). I found one other person with the same problem [1], though it is hard for me to believe I am the only person trying to run KMail on NixOS. The problem turned out to be akonadi starting an instance of mysqld (mariadb) that failed to find an error messages file because it didn't know where it was. Setting the --basedir prevents this problem from occurring, and that is what is done in the service module definition. kdepim users can solve the problem locally by setting basedir in their akonadi/mysql.cf config, but if we would like it to work out of the box it seemed to me that the way forward was to use wrapProgram on mysqld. You can't actually run mysqld from the commandline without without the --basedir argument with it packaged the way it is now anyway. This turned out to not work either because: - wrapProgram --add-flags *prepends* all the wrapped flags to the argument list - akonadi uses the --defaults-file argument - mysqld requires --defaults-file to be the first argument if it is used This can certainly be solved with some hackery after the wrapProgram in postInstall, but perhaps it would be better to include a --suffix-flags feature to make-wrapper.sh. What would you suggest as the better choice? I didn't want to submit a PR with a hack if that wasn't the way forward, and I definitely didn't want to submit a PR touching the build tools and documentation without at least saying hello first. Thank you, Phil Wetzel [1] - http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015575.html ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev