Re: what about Database?
Thanks for all yours feedback. I don't mind talking about database issue
in the devel list. The questions I'm worry about is very hard to track
those questions and once again increase the load of Devel-list. Many people
I know have DB-tool, DB-usage and DB-development for debian type questions
that are not really for devel-list and at the same time the user list
may not able to find a good answer for.
That's why I suggested that. I'm also trying to package my db-tool
into debian but it is still in pre-alpha. I still get a lot of questions
need to ask the existing db-tool maintainer etc. And those questions may
be too low for the devel-list and it would be nice if those questions get
filter from DB-list first. And for some new database like firebird, many
people also be interested to learn about it, (that will not be good for
devel-list and very difficult to get answer form user-list)I'm not sure
what is the procedure of starting a request of starting a mailing list.
But I will support that. May be even unofficeally started at my little
server and see how the respond go.
Please let me know I'm not doing something out of line here.
Thanks
Real Question here: I'm trying to package a Java-Object-Relation-Mapping
+ connection pooling API. The problem is most of the testing I'm running
are under Sun JDK (I'm working on classpath and kissme also, just to let
you know where I stand). If the fact is you will not able to run my package
without NON-debian package, will the package itself able to pass and get
into the officeal list? or I may as well just do it on the side. and leave
it unofficeal?
Thanks
Alex
Florian Weps:
>On Sun, Jun 09, 2002 at 06:53:15PM +0200, Grzegorz Prokopski wrote:
>
>
>>W li?cie z nie, 09-06-2002, godz. 13:46, Florian Weps pisze:
>>
>>
>>>On Sat, Jun 08, 2002 at 06:37:09PM +0200, Giuseppe Sacco wrote:
>>>
>>>
>>>>Il Fri, Jun 07, 2002 at 01:43:12PM -0500, Alex Lau ha scritto:
>>>>
>>>>
>>>>>I don't notice there is any debian-database mailing. Does anyone feel
>>>>>that is neccessary?
>>>>>
>>>>>
>>>>Yes,
>>>>I would like to have a database policy in order to install applications
>>>>that require an SQL engine.
>>>>
>>>>Maybe a database mailing would be the best place where to start a talk
>>>>about it.
>>>>
>>>>If you want to ask for that mailing list I will second it.
>>>>
>>>>
>>>So would I.
>>>
>>>
>>Hmm... I haven't seen so much traffic about databases here.
>>I think that you should first consider trying to discuss the things here
>>and if the traffic grows - then move to separate mailing list.
>>But of course maybe there sth in d-d that prevents successful discussion
>>on this topic? (no idea)
>>
>>
>
>Lots of traffic, which makes it hard to track down DB specific stuff,
>especially in the archives.
>
>
>
>>I would be afraid that this way you would create another deadly silent
>>mailing list with few subscribers.
>>
>>
>
>Debian-games comes to mind. You could be right. I'd like to try anyway,
>and I believe that a debian-db yould be more successful because:
> * debian is not the distribution of choice for gamers
> * debian _is_ popular on web-servers, running CGIs and servlets
> connected to data bases. Think of all the groupware packages.
>Debian-java, for example, is not high-volume, but it is nice to have
>all java related discussion in one place.
>
>
>
>>I am interested in this topic too, but it seems unsure if creation of
>>separate m-l will succeed.
>>
>>
>
>So let's get started discussing here, for now.
>
>For one thing, I am currently packaging SQL Relay, a data base
>connection proxy. See bug #119700 for the ITP. The upstream
>home page is at <http://firstworks.com> Usable packages
>for i386 and powerpc are at <http://web.green.ch/fweps> and
><http://ehec.foorborne-net.de/~wepsf>. Since this software is so diverse
>(many DB engines, many APIs), I can't really test it all by myself;
>I _do_ have testers, but could use more.
>
>Secondly, Giuseppe suggested a policy document for packages that rely
>on a DB engine. I don't see much need for yet another policy document
>(packaging SQL Relay got me in contact with many policy documents -
>all useful, mind you), but maybe I am overlooking some serious points -
>such as what happens to client software when the DB gets updated. What
>are your arguments in favour of a DB-policy, Giuseppe?
>
>
>
>>Regards
>>
>> Grzegorz Prokopski
>>
>>
>
>I am subscribed to debian-devel; no need to To: or Cc: me.
>
>Florian
>
>
>
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: