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

Re: How to deal with "assets" packages shadowing real upstream



Quoting Jonas Smedegaard (2016-02-27 13:08:37)
>> 2. Needless forking is bad.  There is no consent on what is 
>>    "needless" though. My point is that having multiple copies of a 
>>    thing that are all treated as source leads to problems.  In 
>>    Debian, we recognize that and one effect of that is that we don't 
>>    want bundled libraries in packages.  In the greater free software 
>>    community, not everyone sees it this way.  Having this opinion in 
>>    Debian, I think we should use our influence to try to push 
>>    upstreams the right way.  That means we should package real 
>>    upstream if there are multiple sources to choose from.  Another 
>>    reason for doing this is that future code duplication in Debian is 
>>    automatically prevented.  In your example: if someone needs the 
>>    serverside version of the package, they would package 
>>    node-handlebars and then we have two versions of the code in 
>>    Debian.  If the real upstream was used to begin with, that problem 
>>    would have been avoided.
>
> Right.  That is the issue.  Question I raise is how to deal with it?
>
> I agree with you that the real upstream should be used when possible - 
> but is that just the personal opinion of two Debian developers which 
> should not be imposed on others (read: at most file wishlist 
> bugreports) or do we have rough consensus in Debian to make it into 
> Policy, so that issues of that kind can be treated as more severe 
> bugs?

Oh - I just discovered that this _is_ covered by Policy §4.13 already.

I will file severe bugreports whenever I stumble upon this kindof issue 
in the future.  Thanks for helping out!

 - Jonas

-- 
 * 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: