[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fossil-users
Subject:    Re: [fossil-users] C API
From:       Stephan Beal <sgbeal () googlemail ! com>
Date:       2012-01-07 23:41:42
Message-ID: CAKd4nAj7QOJnYsEHC4UzthFacvpbykt6Eft_NOYHWS2Su2s=GQ () mail ! gmail ! com
[Download RAW message or body]

On Sat, Jan 7, 2012 at 11:55 PM, Chad Perrin <code@apotheon.net> wrote:

> On Sat, Jan 07, 2012 at 06:50:22PM +0100, Stephan Beal wrote:
> ...
>
> Search the archives for this group for many very long threads on this
> > topic. Management Summary: it can't be done without what amounts to a
> > complete rewrite, which would be a huge amount of work requiring a good
> > deal of knowledge of how fossil works internally.
>
> Okay, but . . . what about just a general C or Ruby API?
>

My point was: there isn't one, and won't be one until someone volunteers
for the task (and manages to pull it off). Fossil is implemented as a
monolithic application, not an app on top of a library, and internally it
is not at all set up to be run "like a library." Yes, we would all (or
almost all) like to see it be refactored as a lib/app combination, but it
would require a huge effort, far beyond what any of the current
contributors can commit to.

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal

[Attachment #3 (text/html)]

<div class="gmail_quote">On Sat, Jan 7, 2012 at 11:55 PM, Chad Perrin <span \
dir="ltr">&lt;<a href="mailto:code@apotheon.net">code@apotheon.net</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> <div class="im">On Sat, Jan 07, 2012 at 06:50:22PM \
+0100, Stephan Beal wrote:<br>... </div></blockquote><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
class="im"> &gt; Search the archives for this group for many very long threads on \
this<br> &gt; topic. Management Summary: it can&#39;t be done without what amounts to \
a<br> &gt; complete rewrite, which would be a huge amount of work requiring a \
good<br> &gt; deal of knowledge of how fossil works internally.<br>
<br>
</div>Okay, but . . . what about just a general C or Ruby \
API?<br></blockquote><div><br></div><div>My point was: there isn&#39;t one, and \
won&#39;t be one until someone volunteers for the task (and manages to pull it off). \
Fossil is implemented as a monolithic application, not an app on top of a library, \
and internally it is not at all set up to be run &quot;like a library.&quot; Yes, we \
would all (or almost all) like to see it be refactored as a lib/app combination, but \
it would require a huge effort, far beyond what any of the current contributors can \
commit to.</div> <div><br></div><div>-- </div></div>----- stephan beal<br><a \
href="http://wanderinghorse.net/home/stephan/" \
target="_blank">http://wanderinghorse.net/home/stephan/</a><div><a \
href="http://gplus.to/sgbeal" target="_blank">http://gplus.to/sgbeal</a></div> <br>



[prev in list] [next in list] [prev in thread] [next in thread]