| 1 |
* Krzysztof Pawlik <nelchael@g.o> schrieb: |
| 2 |
|
| 3 |
> > Hmm, this document suggests something, I just forgot to prohibit: |
| 4 |
> > |
| 5 |
> > "Release the source archives along with whatever binary archives you may have." |
| 6 |
> > ^^^^^^^^^^^^^^^^^ |
| 7 |
> |
| 8 |
> You intend to "prohibit" releasing binary packages for upstream? |
| 9 |
|
| 10 |
No, I'm talking about precompiled stuff within the source tree. |
| 11 |
Such things should _never ever_ happen. |
| 12 |
|
| 13 |
In Java world it seems to be quite common to bundle precompiled |
| 14 |
imported libraries within the source tree. Needless to say that |
| 15 |
this can easily get hell for any package-based distro. |
| 16 |
(actually, that mostly comes from the windows front, where |
| 17 |
concepts like package management are quite unknown ... ;-o) |
| 18 |
|
| 19 |
> What's important in quoted sentence is: "Release the source archives along with |
| 20 |
> binary archives" - the "with" is very important - in short: don't release only |
| 21 |
> binary versions and force us to grab them from VCS. |
| 22 |
|
| 23 |
Okay, perhaps I misunderstood this sentence. |
| 24 |
|
| 25 |
BTW: if upstream has an proper VCS and an canonical tagging |
| 26 |
scheme, they don't actually have to create release tarballs, |
| 27 |
just hack up a little script which creates them on-the-fly |
| 28 |
from an canonical URL scheme (eg. oss-qm does exactly that). |
| 29 |
|
| 30 |
|
| 31 |
cu |
| 32 |
-- |
| 33 |
--------------------------------------------------------------------- |
| 34 |
Enrico Weigelt == metux IT service - http://www.metux.de/ |
| 35 |
--------------------------------------------------------------------- |
| 36 |
Please visit the OpenSource QM Taskforce: |
| 37 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
| 38 |
Patches / Fixes for a lot dozens of packages in dozens of versions: |
| 39 |
http://patches.metux.de/ |
| 40 |
--------------------------------------------------------------------- |
Archives