Re: Bug#593134: (unreleased) libprophet-perl: GPL in debian/copyright
>>>>> Jonas Smedegaard <dr@jones.dk> writes:
>>>>> On 12-09-29 at 02:42pm, Ivan Shmakov wrote:
>>>>> Christine Spang <spang@MIT.EDU> writes:
[…]
>>> I've updated Prophet's debian/copyright for this (and all the other
>>> javascript and css files shipped with Prophet) in git. Hopefully
>>> it will be uploaded soon; I have some other changes I'd like to get
>>> in first though.
> You should most likely avoid installing that and instead depend on
> (and add symlinks for or similar) the separately packaged libjs-yui.
AIUI, this was already reported as Debian Bug#576628 [1], and
apparently fixed (at least partially) upstream. I hope to look
into it sometime after this debian/copyright issue is resolved.
> You still need to document the licenses - unless you additionally
> repackage to strip those files also from source, but nicest is to
> redistribute pristine source tarball, even if more hassle.
ACK, thanks.
I guess I should try to contact their respective upstream
authors for clarification.
(Alternatively, these files could be removed from Prophet
upstream; I have some doubt if maintaining local copies of these
worth the effort.)
>> share/web/static/jquery/js/hoverIntent.js
> Similarly it seems you should make use of the separately packaged
> libjs-jquery and other packages.
Likewise [1].
> If your source package ships with some JQuery addons or other
> JavaScript libraries not unique for Prophet but convenience copies of
> external projects, then please file RFP bugs about them, and consider
> asking the JavaScript team to get them packaged.
ACK.
>> PS. To note is that, as a avid user of both Lynx and NoScript, I'd
>> be happy to discard all of these. Hopefully I can get the things
>> clarified, however.
> Cool if those JavaScript routines are only optional for Prophet -
> then you need only recommend or suggest those libraries.
It's my understanding they are.
[1] http://bugs.debian.org/576628
--
FSF associate member #7257
Reply to: