|Re: [eigen] [RFC] symbolic computations using eigen|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] [RFC] symbolic computations using eigen
- From: Keir Mierle <mierle@xxxxxxxxx>
- Date: Mon, 2 Feb 2009 17:30:14 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=kOBcJzAgTjE+0gKakCJpyDxlbouRWzki8HndtadvUJc=; b=WrLGZCjUDdmFjG6OIBeNK60SoNQVC2jS6TgKF7WkgXYUX6hdkADI1bsE3DOc/drZ0X EXVpsuukCdFL+0POmq8II+4+Q5M7XQ7H5ofyHdMvwUFUV2/gkvWFezL6JuHFvOc82Kj5 IOTAh1ypr76de2Uyd9+drKToKz8mglnNPPLes=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lnzepGZdwbtF8AYB+JXmkM0BUj+gAhKKelxxAW74463q3qtg4Jx1D7Whvldmv8DJPK C6+tNBmidNh+ONcSzpMHWO2nJ61FWnC5g+0w6K+Wgq3a98Fm37VQZJGezEosILYZr4xf 6mQugEfJBIuYchp7GNcOXNQriP5LJ2/gdVt7I=
On Mon, Feb 2, 2009 at 3:39 PM, Benoit Jacob <jacob.benoit..1@xxxxxxxxx>
> On Feb 2, 2009, at 5:40 PM, Benoit Jacob wrote:Ah, you said _repository_. Interesting.
>>> The classes have been on my hard drive for a while and I thought you may
>>> find these features useful enough for a potential inclusion in Eigen.
>> As for inclusion in Eigen, I think that the main prerequisite for this
>> would be for us to have clear use cases in mind and being confident
>> that we can cover them with good performance.
> One suggestion is that you could offer a "Eigen contributed" repository
Working directly in a subdir of eigen2/ makes this work much more available..
But it requires that contrib/ contributors get a KDE SVN account. Keir
is already getting one anyway, and Timothy's been around for a while
so i guess it makes sense that he gets one too. However, should there
be people contributing only to contrib/, it would be strange to get a
KDE account just for that.
What's wrong with that? Having contrib/ be a staging directory seems reasonable. As something moves from contrib to core, then the maintainer will naturally be able to continue without having to get a different account.
Put another way, what is the harm in being liberal with accounts? (ok, build breakage, but did i hear about a continuous build somewhere?)
So that would justify having a separate
repo. We could have a command in eigen2 to fetch it. Tuxfamily could
provide the SVN or Git repo.
We could do this, but it is just more hassle for users. At this point Eigen is small; let's not add unnecessary steps to get extra contrib packages. By keeping it together, the development rate of contrib/ stuff will be higher. contrib can be split off later if it becomes a burden.
Perhaps rename the contrib directory 'unsupported/' to make it clear that code in that directory may format your harddrive.
I don't know.