What I did is this:
rm -rf ~/.sinan
Wiped my entire DAV repo
Followed your instructions
That worked very well for the library application.
Then I needed to build the app that uses the lib app. As long as I
have uploaded the library *as an application*, the build works fine.
Sinan does not seem to look at it in the repository as a release,
unless I am mistaken (and I am tired enough to be mistaken).
The last remaining problem I have is
/usr/local/erlware/bin/sinan release
starting run
[check_depends] start
[check_depends] stop
[build] start
[build] stop
[release] start
[sin_release_builder fault!!] Duplicated application included:
mylib included in subapp and myapp
Task failed
I must confess I cloned the Sinan git repo, got rid of the "e" in
"formate", rebuilt it using the release Sinan, and then installed the
patched Sinan version using Faxien (I think.... my eyes are crossed at
this stage:), and so we don't see that funny message any more.
But if I don't include the lib app in both the .app files of my main
application, I don't see the .hrl file I need that's in the lib app.
What to do, what to do... do I put the lib under applications, or
under included_applications, some some combination of the two? Or
what?
On Sep 4, 12:32 am, "Martin Logan" <[EMAIL PROTECTED]> wrote:
> Ahh, well, you can do that, but yeah, we need a cook book.
>
> Try this in order exactly as below:
>
> sinan clean
> sinan dist
> faxien publish
> .. follow prompts
>
> what happens?
>
> On Wed, Sep 3, 2008 at 11:24 PM, Edwin <[EMAIL PROTECTED]> wrote:
>
> > What I can't figure out is why I can't just type in
>
> > sinan release (or dist - dunno which)
> > faxien publish /my/dir/mylib-1.1.1.tar.gz
>
> > so that I can later do a faxien install-release and it just works.
> > When I tried that, it uploaded the gz file to the DAV repo, but didn't
> > create anything in the Meta dir that contains the .rel and so on that
> > is needed, so the faxien install-release didn't work (said something
> > about not finding /5.6.3/Meta/mylib). If I install mylib as an app
> > using the directory structure, it works fine. There's something I'm
> > not quite absorbing here.
>
> > What I'd really appreciate is a simple example that ties the two
> > together in a cookbook step-by-step fashion that doesn't tax my aching
> > brain too much...
>
> > On Sep 4, 12:07 am, "Martin Logan" <[EMAIL PROTECTED]> wrote:
> > > Thanks a lot - this kind of thing keeps us going :) Samuel, Dave P,
> > Scott,
> > > Dave S, Eric and I have put a lot of work into this, as have a number of
> > > other folks and I am sure I speak for all when I say thanks for the good
> > > word.
>
> > > As for releases - try running this command:
>
> > > faxien fetch-release erl ./
>
> > > that is going to pull the erl release - in a publishable form down into
> > the
> > > ./ directory. Examine that package, it is pretty straightforward - well
> > > except the executables in the bin file - for those you may want to copy
> > > something more straightforward like the faxien executable script.
> > Basically
> > > copy that structure changing specifics for your release of course and
> > then
> > > publish away. We can help if you have trouble.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
