Skip to content

Releases: melpa/package-build

2.3

27 Jul 19:53
Compare
Choose a tag to compare
  • #22 Do not attempt to skip packages when they are already up-to-date because we ended up not building packages that actually had to be rebuild.
  • #21 Combine author and maintainer cons-cells into a single string before converting the archive alist to JSON because doing so would otherwise fail.

2.2

27 Jul 19:53
Compare
Choose a tag to compare
2.2
  • #20 Define package-build-package as an alias for package-build--package to help Cask.
  • b2b474a Only remove .in suffixes from .el files, as originally intended.

2.1

10 Jun 17:45
Compare
Choose a tag to compare
2.1
  • 56a0ddb Fix a regression in the creation of the recipe JSON file.

2.0

10 Jun 17:44
7733c25
Compare
Choose a tag to compare
2.0

Major refactoring done in #15 and #16.

  • Make code that determines the appropriate version self-contained.

  • Use fewer arguments to pass data around.

  • Use Eieio objects to represent recipes instead of plists. These objects contain more information than the old plists, which is what makes it possible to use fewer arguments to pass information around.

  • Replace leaky abstractions with self-contained functions, doing one thing only, and all of it.

  • Organized the file into logical units by using sections. This was a very necessary step, which I already began in earlier patch series. It helps a lot recognizing accidental complexity and removing it.

  • Remove many helper functions, by inlining them. These helper functions often existed because the functions that called them were to complicated, making it necessary to move at least some of the code elsewhere. But after cleaning up the calling function that often wasn't necessary anymore.

  • Refactor the recipe interface.

    Previously an alist of all available recipe of the form ((NAME . PLIST)...) was compiled from the contents of the recipe files and then being passed around and being cached in a variable.

    To replace that add a function, package-recipe-lookup, that reads a single recipe file and returns a recipe object. Everything else now only deals with such objects. The recipe representation (NAME . PLIST) isn't used anymore, except for on-disk storage. I.e. it is an implementation detail as far as the code is concerned. Of course for submitters of package recipes it is still the primary interface. Internally a package is now always represented by a recipe object or simply by its name. There no longer are any intermediate states.

1.2

10 Jun 17:44
Compare
Choose a tag to compare
1.2
package-build--princ-{exists,checkout}: inline

1.1

10 Jun 17:44
Compare
Choose a tag to compare
1.1
Merge pull request #6 from vermiculus/master

Add commit information to archive.json

Debut release

14 Aug 11:53
Compare
Choose a tag to compare

Initial numbered release following extraction from the main MELPA repository.