summary refs log tree commit diff
path: root/pkgs/build-support/emacs/melpa.nix
Commit message (Collapse)AuthorAge
* Merge pull request #127980 from matthewbauer/darwin-emacs-native-compMatthew Bauer2021-07-15
|\ | | | | Add gcc for emacs wrapper so native-comp works
| * Add gcc for emacs wrapper so native-comp worksMatthew Bauer2021-06-23
| | | | | | | | | | On macos, we don’t have a gcc executable by default, which is required for some reason when compiling site-start.
* | emacs.pkgs.melpaBuild: package-build: 2018-10-05 -> 2021-04-13Alyssa Ross2021-07-06
|/ | | | | | | | | | | I think this is due an update. I've chosen to update to the latest version that has been merged into Melpa. Unfortunately we now need to hack around it trying to run VCS commands. My Emacs configuration with thirty-something leaf packages seems fine after the rebuild.
* emacs: add currently compiling package dirs to load-pathMauricio Collares2021-02-19
| | | | Co-authored-by: Tad Fisher <tadfisher@gmail.com>
* emacsPackages.melpaPackages: HTTPS for homepagesAlyssa Ross2020-12-10
|
* treewide: Remove usage of isNullDaniel Schaefer2019-04-29
| | | | isNull "is deprecated; just write e == null instead" says the Nix manual
* melpaBuild: Get package-build from melpa/package-buildThomas Tuegel2018-11-27
| | | | | | | | This commit causes melpaBuild to use package-build from melpa/package-build instead of melpa/melpa. Development of package-build happens in the former repository whereas the latter is much larger, containing also the MELPA recipes. We do not need to fetch the MELPA recipes from melpa/melpa, as we fetch them one-by-one for Nixpkgs.
* emacsPackagesNg.trivialBuild: cleanup and standardize functionBenjamin Hipple2018-11-27
| | | | | | No real function change here, but this updates the trivial and melpa builders to be formatted more consistently with the rest of the builders, and swaps `eval "$preBuild"` for the more standard `runHook preBuild`.
* Fix pname to ename propagation if nullPeriklis Tsirakidis2018-07-27
|
* melpaBuild: use Emacs package names to satisfy package-buildThomas Tuegel2018-07-23
| | | | | | | | | | package-build expects the recipe file name to match the Emacs package name. `melpaBuild` takes an extra argument `ename` for the Emacs package name (default: `pname`, the Nix package name) which is used to name the recipe file. Fixes: #43893 See also: #43609
* pkgs/*: remove unreferenced function argumentsvolth2018-07-21
|
* emacsPackagesNg: 2018-07-15 updateThomas Tuegel2018-07-15
| | | | | | | All package sets are simultaneously updated to accommodate changes to package-build. Due to new restrictions in package-build, all packages using `melpaBuild` must now provide a recipe file, even those packages which are not included in upstream MELPA.
* elpaBuild: factor out package installationThomas Tuegel2016-01-18
| | | | | | Building packages requires package-build.el from Melpa, but installing packages only requires package.el. Packages from ELPA are already built, so there is no need to involve package-build.el.
* melpaBuild: don't guess archive file nameThomas Tuegel2016-01-18
| | | | | package-build can tell us exactly what the archive file name is, instead of globbing for it.
* melpaBuild: get Emacs package name from recipeThomas Tuegel2016-01-18
| | | | | | When building a package from a Melpa recipe file, get the Emacs package name from the recipe. Nix is more restrictive about packages names than Emacs, so the Nix name for a package is sometimes different.
* melpaBuild: accept recipeFile in lieu of fileSpecsThomas Tuegel2015-12-29
|
* melpaBuild: update package-build.elThomas Tuegel2015-12-27
|
* emacs-packages: add automatic meta.homepages to builders, cleanup other ↵Jan Malakhovski2015-07-31
| | | | | | expressions Because we can.
* refactor Emacs packages'/modes' buildersJan Malakhovski2015-03-03
| | | | | | | | | This simplifies melpa builder by merging with it my old emacs modes builder, adds better instructions and support for overrides in emacs-packages.nix, and renames some emacs-related stuff in all-packages.nix for sanity reasons. I declare this backwards compatible since direct uses of emacsPackages in configuration.nix are very unlikely.
* reorganize emacs related filesJan Malakhovski2015-03-03