Edwin,
Sorry for the slow responses here. The power adapter for my laptop
failed and I am waiting for a new one.
> You know, I am of the old "if weird things are happening and you think
> something is not being kept up to date, blow it all away and start fresh"
> school of thought.
>
> It worked in the older Make days when dependencies were not updated (or
> defined) correctly, and it will work here too (for me, it's not for
> everyone). I think I will create a makefile with a realclean target that
> removes the entire .sinan/repo tree and also calls sinan clean. I will also
> add a faxien publish under a make release target (i.e. sinan dist; faxien
> publish). Then I'll ensure I only use the makefile. I have to do this anyway
> because I have C code Erlang linked-in drivers that need to be compiled, so
> it's no big deal. I don't really care about the time it takes to pull in
> fresh code because I have a local DAV repo, a fast Internet connection, and
> not that many dependencies.
>
> For me, the biggest problem now is the
> include_lib("rabbitmq_server/include/rabbit.hrl") conundrum. Either I build
> and publish RabbitMQ myself (which entails renaming and munging their .app
> file and some other hacks) or I create a fake rabbitmq_server Sinan project
> that contains only the include files. Yuck. If there ever is one day a
> rabbitmq_server that goes into the public Erlware repo it will really screw
> up things! In the meantime I suppose I could do it like this:
I would agree. We need some way to arbitrarily include applications
into the build. Right now Sinan assumes anything it needs is in the
erlware repo. I suspect this can be solved with local repos, yet
another thing on my plate.
>
> Create a sinan project called rabbitmq_server using sinan gen.
> Get rid of the app and supervisor source files.
> Do sed magic to massage the project's rabbitmq_server.app file into shape.
> Copy the contents of the include subdirectory from Rabbit's official release
> into a Sinan project named rabbitmq_server.
> Publish it to my local faxien repo.
> Put an {included_applications} dependency into my project's app file.
You shouldn't have to do that.
>
> The second biggest problem now is the duplicate {include_applications} sinan
> build issue. If I am forced to put dependencies into the {applications}
> tuple, then things that have {mod} in their app files that I really do not
> want to start (like Yaws), but only want to load, have to be messed with. In
> the previous Erlware makefile stuff I munged the .rel file to have "none"
> after it for things I didn't want started. That worked but is butt-ugly. If
> this is an outstanding issue I will have a go at fixing it. Hmm... maybe
> something in the sinan .cfg file that says "disable starting this app,
> overriding whatever the app file says"?
>
> disable_apps : [yaws],
>
> Hmm?
This is a bug that I need to fix. Its my top priority when the power
adapter gets here ;)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlware-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlware-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
