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 -~----------~----~----~----~------~----~------~--~---
