On 2006-02-28 08:40:30 +1100, Gordon Rowell wrote: > John Peacock wrote: > >For the record, my proposal was a contribs/ folder at the top level of > >the qpsmtpd directory, with individual folders for each contributed > >item. This might seem overkill for a single plugin submission, but we > >could easily switch that to a separate folder for each author > > Careful here. We did something similar for e-smith/SME Server and it > quickly became confusing as people built their own "latest" copy of a > package. Although more painful from an auth p.o.v., I think the > subdirectories should be named by plugin, if subdirectories are chosen.
I agree with that.
> I'm in favour of subdirectories, but would also be happy with a single
> contribs/plugins directory.
I'm also in favour of subdirectories.
If there is single directory, I think subdirectories should be created
as soon as a plugin consists of more than a single file. So if I
contribute a plugin "foo" it could be put into contribs/foo. But if I
add a sample config file, the plugin itself should be moved to
contribs/foo/foo and the config file added as contribs/foo/config.sample
(or maybe better contribs/foo/plugins/foo and
contribs/foo/config.sample/foo to fit with the qpsmtpd directory
structure). So files which belong together can always be found in a
single child-node of contribs.
I don't think the structure of subdirectories of contribs should be
prescribed in detail. Usually, there will be just one or two files and
if it gets more complicated, the best layout can be left to the author
of the plugin.
hp
--
_ | Peter J. Holzer | Ich sehe nun ein, dass Computer wenig
|_|_) | Sysadmin WSR | geeignet sind, um sich was zu merken.
| | | [EMAIL PROTECTED] |
__/ | http://www.hjp.at/ | -- Holger Lembke in dan-am
pgpLlFJX84v93.pgp
Description: PGP signature
