Mailinglist Archive: opensuse-bugs (6564 mails)

< Previous Next >
[Bug 528097] default file system is not supported
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 4 Aug 2009 15:18:16 -0600
  • Message-id: <20090804211816.6D809245513@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=528097

User jeffm@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=528097#c7


Jeff Mahoney <jeffm@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |meissner@xxxxxxxxxx




--- Comment #7 from Jeff Mahoney <jeffm@xxxxxxxxxx> 2009-08-04 15:18:15 MDT ---
I'm not advocating a binary-identical solution or a spec file solution. It only
matters that it's source identical. The packages aren't binary-identical and
neither are their contents. They're compatible but not identical. Anything with
a timestamp throws them off.

Here's what I have in mind, using SLE11 and 11.1 as stand-ins for any pair of
closely linked releases.

When I made the decision to use the SLE11 kernel on 11.1, it was to reduce
maintenance load. In particular, it would have taken a lot more time to keep
11.1 synced up with every patch we do against SLE11, so it made sense to use
the same source tree.

With git, keeping them in sync is easy. Immediately before submitting a
maintenance update for both 11.1 and SLE11, we can pull from the SLE11 tree
into the 11.1 tree. All the patches come along for the ride and the only
difference is disabling the enterprise support reporting facility. Users
wanting to ride along for the latest and greatest can use the SLE11 KOTD. Even
if we say that's not good enough, it's easy to automate pulling into the 11.1
branch. If there's a failure, report it. Since the only difference between the
two branches should be the value of CONFIG_ENTERPRISE_SUPPORT, this should be
exceptionally rare.

I'll post my patch to add the option shortly.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References