| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
‘make package’ complains that the directory contents changed while trying to
make the tarball. I assume that's because the tarball is made in the directory
that's being packaged. Moving it should fix this.
|
| |
|
|
| |
This should make it possible to upload all of the contents to sourcehut pages.
|
| |
|
|
|
|
| |
Put everything in public/pakages so that at a later date I can add a project
site along with the packages. This change also makes it easier for me to change
my mind about where the packages land.
|
| | |
|
| | |
|
| |
|
|
|
| |
These packages don't have snippets anymore and therefore aren't multi-file
packages anymore.
|
| |
|
|
|
| |
The gui module now includes SVG icons that need to be installed along with the
configuration.
|
| |
|
|
|
|
| |
This package now contains all of my snippets, instead of having them distributed
across multiple packages. I hope that this will make them easier to manage and
keep updated.
|
| |
|
|
| |
It's just an empty file on my disk that hasn't been committed.
|
| |
|
|
|
| |
Oops, must have accidentally screwed this up when I changed the name. Will
probably move the guile code into its own file at some point, though.
|
| |
|
|
|
|
|
| |
The ‘get-multifile-module-version’ and ‘get-module-version’ functions open up
the given Emacs Lisp file and search for a “Version” header, parses it out, and
then returns the file name of the module as it should look in the package
archive.
|
| |
|
|
|
|
|
|
|
| |
Don't load the user init file while building my Emacs packages, make sure to use
a different ‘package-user-dir’ so that bad packages don't interfere and it
doesn't accidentally work because of existing packages. Specify the
‘package-archive-upload-base’ in the Makefile so that there is only one place to
look and modify if this needs to move. Ensure that the
‘package-archive-upload-base’ exists before uploading to it.
|
| | |
|
| |
|
|
|
|
|
|
| |
This reverts commit cd067e3673a62143ed2e05edf163088c77d35f38.
On the build runner this ends up trying to build ‘oni-scheme.el’ as a multifile
package. It doesn’t seem to notice the distinction between the regular files and
directories.
|
| | |
|
| |
|
|
|
| |
Now that there is a generated.el in the repository, I don’t want to package
_that_ up. A better idea would probably be to move it to some subfolder.
|
| | |
|
| |
|
|
|
| |
In order to differentiate better between the two types of tests, rename the test
commands to unit-test.
|
| |
|
|
|
|
| |
In order to simplify the testing of each package, do the packaging step first so
that when it gets to the testing stage it can load the packaged files from the
local repository and manage the interdependencies that way.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
For now this only contains snippets.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is just an empty package adding some extra snippets for HAML.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
targets
|
| |
|
|
|
|
|
| |
packages
‘oni-conf’ is the first package to include more than one file, it’s mostly a
package to allow distributing snippets.
|
| | |
|
| |
|