Mailinglist Archive: opensuse-packaging (158 mails)

< Previous Next >
Re: Rebase Was: Re: [opensuse-packaging] Package Markup / Package Tagging
  • From: "Dominique Leuenberger" <Dominique.Leuenberger@xxxxxxxxxxxxx>
  • Date: Sat, 04 Sep 2010 20:19:17 +0200
  • Message-id: <4C82A9C5020000290009A984@xxxxxxxxxxxxxxxxxxx>
On 09/04/2010 at 8:13 PM, "Sascha 'saigkill' Manns"
<samannsml@xxxxxxxxxxxxx>
wrote:
Hi Dominique,

Am Saturday 04 September 2010 19:09:53 "Dominique Leuenberger"
<Dominique.Leuenberger@xxxxxxxxxxxxx> wrote:
On 09/04/2010 at 6:33 PM, "Sascha 'saigkill' Manns"
<samannsml@xxxxxxxxxxxxx>

Have we any specs who i can see how it shows in reality?

You can have a look at various packages in GNOME:Factory for example.

GDM in Factory has various patches that are tagged as an exampple

https://build.opensuse.org/package/view_file?file=gdm.spec&package=gd
m&project=openSUSE%3AFactory&srcmd5=c00cf0ae22daaf2184b6451f70096282
For me it looks very good. I'll planning to do that in my Packages too.
What is the difference between FIX-UPSTREAM and FIX-OPENSUSE?

FIX-UPSTREAM: The fix is interesting and relevant for the upstream maintainers
and should, and hopefully has already been, forwarded to the project
team of this very source code.
FIX-OPENSUSE: Those fixes/changes are relevant for openSUSE users or are not
what upstream is interested in.

Look at it like this:
- UPSTREAM mean we should be able to get rid of the patch once again, when this
fix/feature was implemented upstream
- OPENSUSE: We'll probably keep the patch forever. Generally a bad thing and a
pain for package uupdates.

Dominique
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >