Subject: Re: BETA: miniSQL database engine & tools v1.0.16

From: "Darren/Torin/Who Ever..." <[email-masked]>
Date: 12 Jul 1996 15:35:33 -0700

-----BEGIN PGP SIGNED MESSAGE-----

Martin Schulze, in an immanent manifestation of deity, wrote:
>I have worked with the mSQL database engine for some time now and
>decided to package it for Debian Linux.  Unfortunately I'm not the
>only one that works on this, but my counterpart seems to be quite slow
>with answering his mails so I steped forward and finished the package
>without waiting for his replies.

You could've dropped me a note saying "Hey, I'm releasing the 1.0.16
package tomorrow."  I don't have the time nor the desire to fight for
the control of a package.  If you want it, take it.  Just please keep up
on stuff in the FAQ and the mailing list.

Darren
- -- 
<[email-masked]> <http://www.daft.com/~torin> <[email-masked]> <[email-masked]>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Do you have your clothes on? I probably don't. Take yours off. Feel better. @
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @

---

From: Ian Jackson <[email-masked]>
Date: Tue, 16 Jul 96 14:01 BST

Martin Schulze writes ("BETA: miniSQL database engine & tools v1.0.16"):
...
> a) I have splitted the package into 4 parts to provide a maximum of
>    flexibility.
> 
>    - libmsql1
>      contains the shared library (only a static lib on a.out systems)
>      all other packages depend on it.
> 
>    - msqld
>      contains the database engine itself
> 
>    - msqladmin
>      contains some programs to maintain the engine and databases
> 
>    - msql
>      contains user programs to manipulate databases
> 
>    - msqlperl
>      contains a library for perl that provides an easy environment for
>      programing database applications

Just one question - is this really necessary ?  I can see that the
shared library might want to be a separate package, but surely (for
example) the msqld and msqladmin packages want to be the same ?

Is msqlperl not small enough to be included in msql ?

> b) This mSQL package needs a special user id `msql' to maintain
>    databases.  Please make sure that a user and a group with that name
>    exists. (on my system they are uid=gid=25, if you choose different
>    values, you HAVE TO recompile the package)

You'll need to get this fixed, I'm afraid, before putting it in the
distribution.

> c) Does it make sense to put msqlperl into the misc section (it's as
>    free as perl itself), while libmsql1 on which it depends has to go
>    into the non-free section?

No, it'll all have to go in non-free.

Ian.

---

From: [email-masked] (Martin Schulze)
Date: Wed, 17 Jul 1996 13:48:54 +0200 (MET DST)

Hallo Ian!

}> a) I have splitted the package into 4 parts to provide a maximum of
}>    flexibility.
}> 
}>    - libmsql1
}>    - msqld
}>    - msqladmin
}>    - msql

}Just one question - is this really necessary ?  I can see that the
}shared library might want to be a separate package, but surely (for
}example) the msqld and msqladmin packages want to be the same ?

msqld has to run on the machine that contains the engine, msqladmin
and msqldump hasn't.  To get a smart machine that acts as a mSQL
server you only have to install the library and the daemon.  You can
do all maintainance from your workstation if you like to.

Of course, when setting up the machine you have to install msqladmin,
too, but may purge it right after the databases are created.

Otherwise you'll get a mSQL engine whenever you want to install the
admin tools.

}Is msqlperl not small enough to be included in msql ?

I don't think that this would be a good idea, because it comes from a
different source package and is maintained separately.  The same
happens to dbf2msql which I shall package...

}> b) This mSQL package needs a special user id `msql' to maintain
}>    databases.  Please make sure that a user and a group with that name
}>    exists. (on my system they are uid=gid=25, if you choose different
}>    values, you HAVE TO recompile the package)
}
}You'll need to get this fixed, I'm afraid, before putting it in the
}distribution.

I?  Hmm, I'm sure this is Bruce' job, isn't it?  Or shall my preinst
script try to install a new user and group?

Regards,

	Joey

-- 
    / Martin Schulze  *  [email-masked]  *  26129 Oldenburg /
   / To-Zeilen in öffentlichen Nachrichten ist FidoNet-Technologie /
  / <gröll>                                            ^^^^^^^^^^ /
 / ... endlich 'mal wieder ein echt gelungener Witz!!!           /
/                                              -- Rainer Scholz /

---

From: [email-masked]
Date: Wed, 17 Jul 96 13:12 EDT

Martin> I?  Hmm, I'm sure this is Bruce' job, isn't it?  Or shall my
  Martin> preinst script try to install a new user and group?

I cannot find it in the Guidelines, but I think it's still valid: if a
package needs a special user or group id, the maintainer _has_ to register it
in advance with Bruce.

--
Dirk Eddelb"uttel                             http://qed.econ.queensu.ca/~edd