ideas about how to package something

2001-09-05 Thread Brandon L. Griffith
Sorry for the vague Subject:
I maintain a package for OpenVerse http://www.openverse.org
as well I am one of the upstream contributors.
Anyhow, we have a slew of plugins available for OpenVerse. Some are as simple
as executing system commands from the chat window and some are as large as the
program itself, well almost. I'm wanting to package all of these up and was
wanting some input from other ppl on it.
Should I package each plugin seperately or make one large
openverse-plugins.deb? I can see pros and cons of each method, such as the
"dict" plugin requiring the dict program which in turn has its dependencies
and such. If I made one large deb then it would have alot of dependencies. But
if I made several small ones then there would be no problem there, except that
the entire deb for some of the smaller ones would be just a few kb in size.
Could someone else out there give me their opinion on this?
thanks

-- 
  .''`.
 : :' :Brandon L. Griffith  <[EMAIL PROTECTED]>
 `. `' http://people.debian.org/~brandon/
   `-  
Debian GNU/Linux   


pgpTKMF1G5xJa.pgp
Description: PGP signature


Re: ideas about how to package something

2001-09-06 Thread Alberto Gonzalez Iniesta
On Wed, Sep 05, 2001 at 10:50:56PM -0400, Brandon L. Griffith wrote:
> Should I package each plugin seperately or make one large
> openverse-plugins.deb? I can see pros and cons of each method, such as the
> "dict" plugin requiring the dict program which in turn has its dependencies
> and such. If I made one large deb then it would have alot of dependencies. But
> if I made several small ones then there would be no problem there, except that
> the entire deb for some of the smaller ones would be just a few kb in size.
> Could someone else out there give me their opinion on this?
> thanks

Hi,

As you already know, I'm quite new to Debian ;-) but here's my opinion 
from what I've learned/seen here. I'll try to group plugins by 
requirements (ie. all those needing "dict" in a openverse-dict-plugins).
That way you could have the simplest plugins in openverse-base-plugins
(or maybe a better name than 'base') and those requiring more
dependencies in separate packages.

Just my .02 Euro


-- 
Alberto Gonzalez Iniesta
[EMAIL PROTECTED]
 
Give Me Liberty or Give Me Death (Patrick Henry)




Re: ideas about how to package something

2001-09-06 Thread Sebastian Rittau
On Wed, Sep 05, 2001 at 10:50:56PM -0400, Brandon L. Griffith wrote:

> Should I package each plugin seperately or make one large
> openverse-plugins.deb?

I would package them according to their size and external dependencies.
For example, I would package the plugin that requires dict separately,
but would package small plugins that have no external dependencies
together. Also, you could check, whether an external dependency is
really a dependency. If for example the dict plugin is very small, put
it in the main plugin package and make it popup a requester saying
"You need the dict package for this plugin." or something similar if
dict is not installed. That may even be a feature that's interesting
for upstream.

 - Sebastian