[csw-maintainers] Handling of devel package splits

[Philip Brown]

The poll is inadequately described. For such a critical, major policy
change such as this, you must be more explicit.

The poll should describe what "split off devel" means.

First, (presuming this is your intent), you should explicitly say,
"MUST split off _devel".
then you need to describe everything that should go in there.

ALSO, you did not adequately describe potential justifications for
when things should be split off vs not, for the "case by case basis".

For example, the criteria that I personally use, are the following:

a) Any time a maintainer wishes to provide a static library, it should
be done in a separate _devel package
b) when there are excessive amounts of development specific
documentation, that belong more in a
  _devel package, than a _doc package. (eg: if there is substantial
user documentation, but also substantial development documentation),
it MAY be a good idea to split off the devel docs.
c) when there's a bunch of development-useful-only tools, it MAY be
useful to split them off.

Generally speaking, when splitting off devel stuff saves 20% of the
package, or a megabyte or more of download size.

HOWEVER, none of the above to me are really important, if the _devel
package is going to be something silly like 20k in size. or if a
single combined package is going to be "small" anyway.


The particular case in point:
Dago is interested in splitting up "xpm", into "libxpm", and "libxpm_devel".

The entire package, if it were one package, is 155k for sparc, and 88k for x86.
The "devel" package, is 5k. yes, 5830 bytes.