OpenLayers 2.5 Debian Packaging

[Christopher Schmidt]

It looks like this goes about halfway, and follows a similar pattern to
what I did for the bits it does. I just added a lot more fluff around
it, especially the actual linking of it into Apache.

I'd like to see a discussion about how to package JS libraries, flash
bits and similar on the debian-webapps list, and perhaps something
http://webapps-common.alioth.debian.org/draft/html/
I imagine checking out the fckeditor packaging would also be
instructive for openlayers packaging.

fckeditor has the same problem as the earlier packaging for OpenLayers
-- it does not include anything to actually enable the application to be
used, other than a comment in README.Debian.

This is in violation of the "should" suggestions in
http://webapps-common.alioth.debian.org/draft/html/ch-httpd.html.
(Obviously not a bug -- simply a lack of functionality.)

I've CCed debian-webapps, though in the past 5 months there have only
been 4 non-spam threads on that list, so I don't know how much response
this will draw in.

For context to debian-webapps: this discussion is about packaging of
OpenLayers, a Javascript web mapping library. The current debian
packaging materials are in
http://svn.openlayers.org/sandbox/crschmidt/debian/ , and as best I can
understand, it meets all the requirements of the webapps-common draft
policy. A thread was started at:

http://lists.alioth.debian.org/pipermail/pkg-grass-general/2007-December/002931.html

and should be read for more context.

I've subscribed to both lists.

Regards,

[sean finney]

hi there,

Post by Christopher Schmidt

It looks like this goes about halfway, and follows a similar pattern to
what I did for the bits it does. I just added a lot more fluff around
it, especially the actual linking of it into Apache.

I'd like to see a discussion about how to package JS libraries, flash
bits and similar on the debian-webapps list, and perhaps something
http://webapps-common.alioth.debian.org/draft/html/

that would certainly be nice. in the case of flash etc, i imagine most of
that could be addressed with a sentence or two about where the files should
be located (since it's from an objective view it's just data being fetched
from the webserver, right?)

but about javascript, maybe it's a little trickier since it's more of
a "library" used by other applications. for example the fckeditor mentioned.

Post by Christopher Schmidt
fckeditor has the same problem as the earlier packaging for OpenLayers
-- it does not include anything to actually enable the application to be
used, other than a comment in README.Debian.
This is in violation of the "should" suggestions in
http://webapps-common.alioth.debian.org/draft/html/ch-httpd.html.
(Obviously not a bug -- simply a lack of functionality.)

which "should" suggestion does it violate? i'm not convinced that it should
be a policy violation not to enable a web application, assuming that it's at
least documented in a README or examples file somewhere. my reading on that
section is that "_if you are going to register yourself with a webserver,_
then the following applies".

Post by Christopher Schmidt
I've CCed debian-webapps, though in the past 5 months there have only
been 4 non-spam threads on that list, so I don't know how much response
this will draw in.

sadly, yes, it's been pretty quiet. for me personally my job description has
changed a bit so i spend less time in the webapp world.


sean

[Christopher Schmidt]

Post by sean finney
hi there,

Post by Christopher Schmidt

It looks like this goes about halfway, and follows a similar pattern to
what I did for the bits it does. I just added a lot more fluff around
it, especially the actual linking of it into Apache.

I'd like to see a discussion about how to package JS libraries, flash
bits and similar on the debian-webapps list, and perhaps something
http://webapps-common.alioth.debian.org/draft/html/

that would certainly be nice. in the case of flash etc, i imagine most of
that could be addressed with a sentence or two about where the files should
be located (since it's from an objective view it's just data being fetched
from the webserver, right?)
but about javascript, maybe it's a little trickier since it's more of
a "library" used by other applications. for example the fckeditor mentioned.

This also is true for OpenLayers.

At this point, I've done my best: I don't know where the logical path is
from here forward.

Post by sean finney

Post by Christopher Schmidt
fckeditor has the same problem as the earlier packaging for OpenLayers
-- it does not include anything to actually enable the application to be
used, other than a comment in README.Debian.
This is in violation of the "should" suggestions in
http://webapps-common.alioth.debian.org/draft/html/ch-httpd.html.
(Obviously not a bug -- simply a lack of functionality.)

which "should" suggestion does it violate?

Weird. I don't know what mulled wine I was drinking when I noticed this,
but I can no longer find the reference that I thought I was referring to
:)

Post by sean finney
i'm not convinced that it should
be a policy violation not to enable a web application, assuming that it's at
least documented in a README or examples file somewhere. my reading on that
section is that "_if you are going to register yourself with a webserver,_
then the following applies".

Yep.

Regards,