1 |
On Montag 25 Januar 2010, Nikos Chantziaras wrote: |
2 |
> On 01/26/2010 12:06 AM, Volker Armin Hemmann wrote: |
3 |
> > On Montag 25 Januar 2010, Alan McKinnon wrote: |
4 |
> >> On Monday 25 January 2010 23:11:18 Nikos Chantziaras wrote: |
5 |
> >>>> Today it is finally released. I don't know why it took so long. :) |
6 |
> >>> |
7 |
> >>> It's a bit sad though that an open source project keeps secrets... I |
8 |
> >>> found out that the tarballs were available for days now but only for |
9 |
> >>> maintainers of KDE packages of various distros. For example Arch Linux |
10 |
> >>> had RC2 binaries available in its [kde-unstable] repo since Jan 21, but |
11 |
> >>> no one would give a link to the tarballs used to build the sources |
12 |
> >>> because they are "secret". |
13 |
> >>> |
14 |
> >>> Am I the only one to find this frustrating (to say the least)? |
15 |
> >> |
16 |
> >> There's nothing secret here. Nothing to see, move along folks. |
17 |
> >> |
18 |
> >> The code is always available in svn, if you wanted it that bad you could |
19 |
> >> have checked it out. It's common release engineering practice to build |
20 |
> >> a tarball from the repo and provide limited access to *those* files to |
21 |
> >> distros and mirrors to give them time to sync and build their binaries |
22 |
> >> before making them available to the public. I mirror Ubuntu and Fedora. |
23 |
> >> The deal is that I get the rpms and debs two days before the public |
24 |
> >> does. This is so that every official mirror on the planet is ready to |
25 |
> >> simultaneously publish the release *all*at*the*same*time*. |
26 |
> >> |
27 |
> >> This is a very excellent way of working. You have no idea how much chaos |
28 |
> >> thousands of eager beaver users cause pounding away at my inbox if I |
29 |
> >> don't have the latest Ubuntu for them the day it is released because |
30 |
> >> sharks bit the undersea cable to London and the inbound bandwidth slows |
31 |
> >> to a crawl. I'm not making this up - stuff like this happens. |
32 |
> >> |
33 |
> >> Gentoo erred in publishing ebuilds for tarballs that were not generally |
34 |
> >> available yet. |
35 |
> > |
36 |
> > no, the user erred in stupid unmasking. |
37 |
> |
38 |
> The user used the provided unmask file |
39 |
> (Documentation/package.unmask/kde-4.4). |
40 |
> |
41 |
|
42 |
before release. |
43 |
|
44 |
Gentoo has a proud tradition of providing the ebuilds before the software is |
45 |
released so as soon as the tarballs hit the mirrors you can start compiling. |
46 |
|
47 |
If you unmask earlier and get errors you are the only person to blame. |