It's been about a year since I last checked on this. I'm really not sure what the method to proceed here is -- am I going to have to custom build my own package for Apache when we move to Debian Jessie?
On Sun, Jun 7, 2015 at 5:04 PM, Steven Sumichrast < steven.sumichr...@gmail.com> wrote: > Forgive my ignorance, I'm not very familiar with the packaging structure > for debian (beyond being a consumer) -- is Upstream from Apache? (I just > went and downloaded 2.4.12 from Apache's site and I see in configure that > you have to pass a parameter to actually enable compiling for imagemap. I > assume this is what we're referring to?) > > The site using these server-side maps probably has hundreds of them in > use. Converting them to user maps is going to be a significant chore. > While I can probably provide the guidance and suggestion to do so, I can't > say that will be done in any short order, so for the interim yes the module > is required. > > On Sun, Jun 7, 2015 at 4:37 AM, Jean-Michel Vourgère <nir...@debian.org> > wrote: > >> Control: tags -1 moreinfo >> >> On May 24th 2015, Steven Sumichrast wrote: >> > In Wheezy 7.8 mod_imagemap was shipped with the apache2.2-bin package ( >> > https://packages.debian.org/wheezy/amd64/apache2.2-bin/filelist). It >> > appears that in the new stable system, apache2.4-bin is missing >> > mod_imagemap ( >> https://packages.debian.org/jessie/amd64/apache2-bin/filelist). >> > I'm not aware of the module being renamed. >> > >> > Additionally the module is not available for install via a standalone >> > package. >> >> Hello >> >> Upstream decided to disable this module by default. >> >> The main argument, as far as I can tell, is that the client side image >> maps have been added in HTML 2.0 (Netscape version 1.4, circa 1992) and >> this is totally obsolete on the server side. >> >> The module code is still available upstream, it was just disabled, and >> it is theoretically possible to add it back in Debian. But isn't it best >> to stick to upstream decisions? >> >> Do you really need that module or was that just a configuration error on >> upgrade? >> >> -- >> Nirgal >> > >
