-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Warnings & Errors #5
Comments
This is wonderful, thanks for the initiative! And I guess this is a good time to learn more about Guix too. Do you use Guix the package manager or the whole distribution? |
I use both the package manager and the distribution. Usually I'm using the package manager on systems where the distribution is performing some kind of critical task for me, like a commercial NAS distribution. Ludovic Courtès just did a wonderful post touching on a few of the things I really appreciate about Guix: reproducibility, and a kind of rationality about the software you use, and how it all fits together. If you do decide to try Guix to help with development, please let me know. Usually what this looks like is placing a Finally, please don't feel the need to formalize your development process on my behalf. I understand that you are in the exploratory phase, and I wouldn't want you to slow down. Maybe tagging stable commits would be enough. You will never break a working Guix package because of the aforementioned reproducibility guarantee. Thanks for the consideration! |
@kat-co sorry it took longer than expected because I was playing around with guix. It seems things work from my latest commit.
Why didn't you need the |
Thank you so much! I've been trying to package your commits every day! I'm so happy I can try You are correct that you need the Re.
Also, when the package definition is not local to your project, and is instead written for Guix, or a Guix channel (as I have done here, it must have a proper But when you are writing the package to be checked in at the root of your source (i.e. like a
which expects a file that returns (and in Guile, like emacs-lisp, that means is the last form declared) a package, and not a module. In this scenario, you want the I hope this all helps. It would be very nice to have a Finally, you may close this issue if you like! Or, we can continue discussing things here. Thank you for the consideration! |
As I'm experimenting with this, I noticed the package definitions we've been discussion would omit the (arguments
`(#:include (cons "^molds/" %default-include))) Also, the inputs should be |
Upon executing `(require 'moldable-emacs) I receive:
I had not seen or used moldable-emacs/moldable-emacs.el Lines 134 to 140 in 13d909b
I think you need a |
Amazing explanation, thanks! You are correct, sometimes I write tests inline: I will move those in a dedicated file so we don't need that requirement here. |
Done, moved the tests in a dedicated file. Also opened #8 for the Guix recipe (although I didn't run the recipe yet myself, I just built it for now) |
Success! And There are still quite a few warnings you may or may not want to take a look at. Things I would consider:
New Build Log
|
Yeah thanks, I have to schedule a refactoring session in which I make the code look proper. |
Hello! I am very excited by this work, and I wanted to try it out. To do so, I created a Guix package both because I use Guix and I wanted to start playing around, and because Guix builds in a clean-room environment and helps me to understand what software actually needs and does.
Here is the package definition:
Unfortunately I got a build error:
Build Log
I know this is a very new mode, so I was wondering if there is a stable commit I can use to start? And if you find this helpful, Guix is a very handy tool to guide development, and can be used on any Linux distribution.
The text was updated successfully, but these errors were encountered: