Ideas/suggestions

[tverlaan]

Hey! Just today I came across your deb packager for exrm. It is about a month ago I wanted to start on this myself but didn't find the time. It's really cool that in the mean time someone else started on this. It looks very promising (!) and I used it just now to see how it comes along.

I ran into an error about a missing description in the deb, should the latest github version work? The hex version had a problem with finding the changelog template, but that's already fixed in master. fixed

I also have some ideas or maybe suggestions and would like to know your thoughts about it:

• configuration of the release in /etc/APP_NAME (together with optional conform file)
• start script in /usr/bin
• everything else in /usr/lib/APP/VERSION/FILES_HERE
  This should make it look more like a regular debian package, correct?

I'm also interested in replacing tar with erl_tar or looking at how to implement upgrades. Can I just start working on those topics or is there some way in which you would like contributions? merged

[johnhamelink]

Hey there 😄

The latest github version should work, I'm awaiting confirmation of #6 before releasing.

Update: The latest github version is now confirmed working (as well as the last release).

• configuration of the release in /etc/APP_NAME (together with optional conform file)
• start script in /usr/bin
• everything else in /usr/lib/APP/VERSION/FILES_HERE This should make it look more like a regular debian package, correct?

All good ideas! I think it makes most sense for the config and start scripts simply be symlinks of the /usr/lib/ files & directories - that would make it easier to distribute.

I'm also interested in replacing tar with erl_tar or looking at how to implement upgrades.

Brilliant! Same goes for ar which is not a particularly common compression format - it'd be nice to not depend on that.

As far as upgrades go, I wonder if it'd make more sense to have standard scripts for apt's install/remove/upgrade hooks which users can then provide scripts to extend it with?

Can I just start working on those topics or is there some way in which you would like contributions?

Not really, just work on whatever you like and submit a Pull Request.

Thanks for your interest in contributing, and I hope to see a PR or two (or three!) in the future.

[crownedgrouse]

Hi, exrm_deb is using my project 'swab' for fakeroot I guess, but you can also get rid of 'ar' with https://github.com/crownedgrouse/edgar ...

[crownedgrouse]

or use directly https://github.com/crownedgrouse/debbie to get rid of any command line !

[johnhamelink]

@crownedgrouse first of all, thank you for building those projects - they look great! I'd like to explore the idea of using debbie to package up the .deb. Would you consider releasing these projects (debbie, swab, edgar, etc) on hex.pm?

[crownedgrouse]

I will consider this . I'm newbie to hex.pm I admit. and a total noob in elixir. BTW you are already using 'swab' via git for exrm_deb .

[crownedgrouse]

Hi john, trying to publish but get stuck in the mud with :

 mix  hex.user register
Compiling 1 file (.erl)
The task "hex.user" could not be found

any tip ? cannot find help on google. This is probably something obvious, but...

[crownedgrouse]

hum forget... mix local.hex !

[crownedgrouse]

Hi john, you can fetch debbie, edgar and swab in hex.pm .
debbie is depending of two others, but I could not add dependencies in debbie's mix.exs. got this :

Error while loading project :edgar at /home/eric/git/debbie/deps/edgar
** (Mix) Trying to load Edgar.Mixfile from "/home/eric/git/debbie/deps/edgar/mix.exs" but another project with the same name was already defined at "/home/eric/git/debbie/mix.exs"

maybe it is because debbie is not an OTP application but a simple module ?.
Any tip welcome.
So at this time, you need to add dependencies to three project to let debbie work.

[crownedgrouse]

Note you can get rid of uname by reading those files :

/proc/sys/kernel/hostname 
/proc/sys/kernel/ostype 
/proc/sys/kernel/domainname 
/proc/sys/kernel/version 
/proc/sys/kernel/hostname 
/proc/sys/kernel/osrelease 
/proc/sys/kernel/ostype 
/proc/sys/kernel/version 

uname is reading anyway those files, endly.

[johnhamelink]

@crownedgrouse just leaving you a quick note to let you know I've not forgotten about this conversation! I've been quite busy recently and haven't had the chance to look through this properly! Thanks 😄

[crownedgrouse]

No problem John. I know what busy can mean.

[crownedgrouse]

will the magic of Christmas work ? :>)

[crownedgrouse]

Hello John, seeing your postie project in Erlang mailing list, and remind me that there was this subject. Any update?