[plt-scheme] PLaneT package organization: looking for advice

I struggled with this same question for the science collection.  I opted for
individual modules that are grouped into sub-collections and finally into
one super collection to be distributed with PLaneT.  They are distributed as
a single .plt file, which makes it somewhat easier for me to distribute them
(particularly to have a single reference manual).  The user typically
'requires' just the modules they need in their code.

Others have made the other choice to create individual PLaneT collections
for each module.

Doug


-----Original Message-----
From: plt-scheme-bounces at list.cs.brown.edu on behalf of Carl Eastlund
Sent: Sun 6/11/2006 12:44 PM
To: PLT Scheme Mailing List
Subject: [plt-scheme] PLaneT package organization: looking for advice
 
If I have a bunch of small, unrelated utilities to provide as PLaneT
packages, is there a standard practice as to whether I should create
several small packages with a single file each, or one package with a
generic name containing several different files (and a blurb
explaining what all the contents are)?

-- 
Carl Eastlund
"Cynical, but technically correct."
_________________________________________________
  For list-related administrative tasks:
  http://list.cs.brown.edu/mailman/listinfo/plt-scheme