[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704196: marked as done (ITP: libraries - Drupal module for shared library management)

Your message dated Mon, 27 Jan 2014 10:45:09 +0100
with message-id <52E62AA5.7030007@pocock.pro>
and subject line accepted
has caused the Debian Bug report #704196,
regarding ITP: libraries - Drupal module for shared library management
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
704196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704196
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Daniel Pocock <daniel@pocock.com.au>

Upstream:

  http://drupal.org/project/libraries

License:

  GPL v2 or later

Comments:

This Drupal module allows other Drupal modules to share common code.

Typically, the common code is a third party JavaScript library that is
not wrapped in a Drupal module package itself (Drupal, like Debian,
prefers to avoid embedded library code)

The module appears to be suitable for use with many Debian-packaged
JavaScript libraries.  Each Debian-packaged JavaScript can be made
available in Drupal by creating a symlink from
/usr/share/javascript/something to
/usr/share/drupal7/libraries/something.  As part of this packaging
effort, I will look at whether to automatically create such symlinks for
all installed JavaScript code, or how to allow other packages or the
sysadmin to conveniently create such links as they are required.

I have already tested this paradigm with sipml5 and the drucall module.

--- End Message ---
--- Begin Message --- 
The package has been accepted already but the bug was not closed

--- End Message ---
Reply to: