summary refs log tree commit diff
path: root/pkgs/build-support/skaware
Commit message (Collapse)AuthorAge
* skawarePackages.buildPackage: add me as maintainerAlyssa Ross2021-06-16
|
* treewide: fix double quoted strings in meta.descriptionvolth2021-01-24
| | | | Signed-off-by: Ben Siraphob <bensiraphob@gmail.com>
* treewide: stdenv.lib -> libPavol Rusnak2021-01-24
|
* skawarePackages.cleanPackaging: copy docFiles before rm noiseProfpatsch2020-05-21
|
* skawarePackages: support static builds via pkgsStaticProfpatsch2020-03-30
| | | | | | | | | | | | | | Most of the skaware packages already build just fine with pkgsStatic, however the wrapper scripts for execline and stdnotify-wrapper needed the `-lskarlib` argument to go at the end. `utmps` and `nsss` still fail with this error: ``` exec ./tools/install.sh -D -m 600 utmps-utmpd /bin/utmps-utmpd /build/utmps-0.0.3.1/tools/install.sh: line 48: can't create /bin/utmps-utmpd.tmp.479: Permission denied make: *** [Makefile:121: /bin/utmps-utmpd] Error 1 ```
* buildSkawarePackage: use pname and version directlyProfpatsch2020-03-30
|
* Revert "buildSkawarePackage: pass through extra args"Profpatsch2020-03-30
| | | | | | | | | | | | | | This reverts commit a50653295df5e2565b4a6a316923f9e939f1945b. The reasons cited were “debugging”, in which case you can just add the attribute to `buildSkawarePackage` and “customizing”, which is still possible with a normal `overrideDerivation`. The patch removed `outputs` for some reason (possible oversight), so building nsss failed. Plus lots of complexity (e.g. don’t forget to add new arguments to `removeAttrs` otherwise there’s a bug now).
* buildSkawarePackage: pass through extra argsAlyssa Ross2019-12-16
| | | | | | This allows things like hooks other than postInstall to be passed through to mkDerivation, which is very useful when customising or debugging a package.
* Revert "skawarePackages.execline: wrap execlineb with tools"Profpatsch2019-10-18
| | | | | | | | Using wrapProgram adds a call to `bash` around every call of `execline`, which clearly misses the basic idea behind `execline` in the first place … This reverts commit b64d25c44782027414509460c1900646dee57db1.
* treewide: remove unused variables (#63177)volth2019-06-16
| | | | | | * treewide: remove unused variables * making ofborg happy
* build-support/skaware: factor out clean packaging utilsProfpatsch2019-02-25
| | | | They are useful for other packages as well.
* skawarePackages.execline: wrap execlineb with toolsProfpatsch2019-02-23
| | | | | | | | | | The execlineb program is the launcher (and lexer) of execline scripts. So it makes a lot of sense to have all the small tools in scope by default. We append to the end of PATH so that they can be easily overwritten by the user. Co-authored-by: Alyssa Ross <hi@alyssa.is>
* skaware: switch from git repos to tarballsProfpatsch2018-09-06
| | | | It should be more performant this way.
* skawarePackages: factor out the common partsProfpatsch2018-09-06
Introduce a `skawarePackages.buildPackage` function that contains the common setup, removing a lot of duplication. In particular, we require that the build directory has to be empty after the `fixupPhase`, to make sure every relevant file is moved to the outputs. A next step would be to deduplicate the `configureFlags` attributes and only require a `skawareInputs` field.