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

How to deal with "assets" packages shadowing real upstream



Hi,

Do we favor tracking the true upstreams when packaging for Debian?

Concretely I need¹ a javascript library for server-side use, but the 
maintainer considers it adequate² to package that project only 
browser-optimized.

I personally feel it is a bug to not track the true upstream of a 
project, but that seems not part of our Policy.  Should I respect fellow 
package maintainers prioritizing convenience over elegance, or insist 
that we should strive towards perfection?


 - Jonas


¹ I am initially packaging kss-node - bug#816003

¹ bug#809977 requests adding node-handlebars to src:libjs-handlebars (to 
cover not only browser but also server-side use), but package maintainer 
chose to instead package libjs-handlebars from a Ruby bundling 
(re)source (see changelog entry for ruby-handlebars-assets 2:0.20.1-3, 
written some months after bug#809977).

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: