Hi,
The secret-project README says to do stack build
.
Doing that gives me a clean compile.
But what deliverable should I have now?
Snippet from secret-project.cabal
:
Executable propellor-config
Main-Is: config.hs
But I don't have a propellor-config
.
Running propellor
gives compile errors.
So that doesn't seem the next step for getting any deliverable.
For what should I be looking??
Cheers
Geert Stappers
I've added some hints to the README, of course it's been a while since I ran it and I only ran it a couple times. The content of the config.hs is really more important than the gory details of how to run it, in my opinion.
thanks
got another error that I probaly can fix my self
Hi,
I feel stupid because I'm still stuck.
What I have is ''secret-project'' from git, commit 14433a9494ed2946c8683a19a13dde54eae64723, Author: Joey Hess joeyh@joeyh.name, Date: Sat Dec 30 13:38:06 2017 -0400
I, stappers, work on host with FQDN paddy.gpm.stappers.nl so I have these changes:
When I follow the instructions from README I get:
How do I get unstuck??
After applying this
is
stack build
happy.But help needed for:
I think this is more bad documentation on my part; probably running propellor like that does not fully work and only the propellor --spin method will really work currently.
(Kind of a bug in propellor to; chroot localdir issue)
Oh yeah, I forgot that needs first:
Since propellor 5.2.0 certianly does include the Propellor.Property.Installer.Types module, I guess you either have a somehow lost file on your local system there, or perhaps you installed a unreleased version of propellor 5.2.0 from git before that file was added to it.
.stack-work
directory I got beyond the Installer.Types error.Perhaps I don't understand the secret-project and its special buid with stack.
I have a git repo in
~/.propellor
and I have a git repo in~/src/secret-project
.In the ~/secret-project directory
The
/usr/local/propellor/
has already a .git directory from ~/.propellor ...The
in previous comment should have been
Yes, I also found it kind of annoying to need to move /usr/local/propellor out of the way when I was working on secret-project. This is why I'd like it to be usable without propellor --spin so that directory would not be used, but until the bug with that can be fixed, you can't work on secret-project with an unrelated other propellor config at the same time.
I got my copy of
secret-project
byDuring build it tries to contact git.joeyh.name
How to avoid connecting to git.joeyh.name during build?