❦ 21 mai 2016 14:55 +0800, Paul Wise <pabs@debian.org> :
>> For some languages, embedded copies are a pattern. Notably Go. But there
>> is also the omnibus stance: the embedded copy could not be in the
>> source, but could be in the shipped artifact. This includes Go, JS and
>> Java (when using uberjars). For some other ecosystems, the embedded copy
>> is more the exception than the rule (C, C++, Python).
>
> By shipped artifact, it sounds like you are talking about source
> packages? or do you mean binary packages?
I meant binary packages but wanted to be more general (not limited to Debian).
>> If upstream is using embedded copies, they are quite unlikely to make
>> any effort tu undo this aspect.
>
> I see upstreams doing that on debian-mentors reasonably often,
> especially when the upstream is the one doing the RFS. For upstreams
> who aren't interested in getting their software into Debian, that is
> definitely the case.
I shouldn't have made a generality. Some upstreams are more receptive
than others to this problematic.
--
Each module should do one thing well.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature