Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Fedora Development (http://www.linux-archive.org/fedora-development/)
-   -   Stable Release Updates types proposal (http://www.linux-archive.org/fedora-development/340486-stable-release-updates-types-proposal.html)

Benny Amorsen 03-12-2010 11:57 AM

Stable Release Updates types proposal
 
Kevin Kofler <kevin.kofler@chello.at> writes:

> If the application is in Fedora as all applications eventually ought to be,
> we will take care of rebuilding it. Otherwise, whoever built it (some third-
> party repository or the user him/herself) is responsible for rebuilding it.
> This has always worked fine, I don't see the problem.

This is pretty harsh for in-house applications for companies. We'll have
to watch the updates, rebuild the in-house applications, and deploy them
to the internal repository on the day that they go into Fedora. Not the
day before or the day after, because that would break dependencies.

You can argue that such places should not accept unfiltered Fedora
updates at all but run their own update servers.

You can also argue that such places should pick a different
distribution, because Fedora can't cater to everyone.

Just please make sure the policy is announced so that we can act
sensibly. Especially if the policy is "Gnome libraries won't require
rebuilds during a release, whereas KDE libraries might".


/Benny

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Kevin Kofler 03-12-2010 02:21 PM

Stable Release Updates types proposal
 
Benny Amorsen wrote:
> Just please make sure the policy is announced so that we can act
> sensibly. Especially if the policy is "Gnome libraries won't require
> rebuilds during a release, whereas KDE libraries might".

The current policy (or lack of a formal policy, if you prefer) boils down
to: "any library might theoretically require rebuilds during a release,
though in practice this is extremely unlikely to happen for libraries with
many dependent packages". Of course neither GNOME nor KDE can be upgraded to
a version which requires rebuilding everything. On the other hand, libraries
such as kdegraphics' libkipi which only a few apps depend on have indeed
been bumped. (For KDE, I refer you to upstream's ABI policy, which basically
says that kdelibs and kdepimlibs are guaranteed to keep backwards binary
compatibility throughout the whole lifetime of KDE 4, but libraries provided
by application modules (i.e. all the other modules) are only guaranteed to
keep backwards binary compatibility within a 4.n series.)

Kevin Kofler

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


All times are GMT. The time now is 02:35 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.