[bknr-devel] Merging development branch

Tchavdar Roussanov troussan at gmail.com
Wed Oct 25 04:04:10 UTC 2006


Yes, the open source world is not the ideal world.

On your question about portableserve the answer is yes, cvs version is
better for me. The same is true for CXML.

Tchavdar

On 10/24/06, Hans Huebner <hans.huebner at gmail.com> wrote:
>
> Hi Tchadvar,
>
> I did merge back from branches/xml-class-rework to trunk.  This
> includes the latest releases of the thirdparty packages as well as the
> current development version of the applications I presently support.
> I started cleaning up some of the cruft that is in the tree and unused
> since years, but there is still a lot to be desired.
>
> About portableaserve:  I am not interested in threading, so I have not
> followed what is needed to make paserve thread save.  I've quickly
> checked the paserve ChangeLog and there seems to have been little
> activity.  Is the latest CVS version any better?   If it helps, I can
> try importing the last version into the thirdparty/ tree.
>
> I have thought about removing thirdparty/ altogether, relying on
> asdf-install instead.  My recent experience with various open source
> packages made me abandon that idea.  I will continue to keep all
> packages that I depend on in the bknr repository and update that with
> recent releases of packages that are used.  I also try contributing
> back fixes to thirdparty/ packages, but I have found trying that being
> pretty frustrating.  Many authors do no longer use (and support) the
> packages they once wrote, and one can be lucky to get a response to a
> mail with a patch at all.  I do like the idea of sharing, but I also
> like getting things done for my customers and it is frustrating enough
> having to spend much more time fixing bugs in software others wrote
> than on the application itself.
>
> Sorry, I just had to write this down somewhere :)
>
> -Hans
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bknr-devel/attachments/20061024/50d6e029/attachment.html>


More information about the Bknr-devel mailing list