Mailinglist Archive: yast-devel (132 mails)

< Previous Next >
[yast-devel] Bugfix vs. ongoing development
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Thu, 25 Oct 2007 13:07:41 +0200
  • Message-id: <20071025110741.GB6631@xxxxxxxxxxxxx>
[I changed the subject since it is a general problem]

* Katarina Machalkova <kmachalkova@xxxxxxx> [Oct 24. 2007 18:41]:
Ahoj!

Hallo !


The problem:
* To test a bugfix, I need to build yast2-ncurses.
* To build y2-ncurses, I need libzypp headers (happen to lose them somehow
during numerous upgrades)
* Tried libzypp svn checkout and then cmake & make, but oh my ... it wants to
download tons of satsolver cr ... I mean, data ;-)
* Trying to skip this by going directly into libzypp/zypp subdir, it
complains
about missing libsatsolver-devel
* OK, trying to compile sat-solver stuff - no success, I miss some rpmdb stuff
* I'm giving up and going to have a joint ;-)

Well, there is no easy solution to this.

The current way of development is

- trunk for everything
- branches for product maintenance

and your example shows that this is not sufficient.

What you (and probably others too, I wonder why noone else speaks up)
need is a 'dedicated bugfix branch' not influenced by ongoing
development in other areas.

In other words: More branches.

Although branching is relatively easy with svn, merging is not and thats
why we limit the number of branches.

My proposal would be to use a different scm (source code management)
system which makes branching and merging less painful, e.g. 'git'

Git would certainly help with scenarios you described (because the
sat-solver kids would play in their own sandbox ;-)) while also
making YaST development more open towards community contribution
(esp. because one doesn't need write access to a central repository).

The downside is a complete new concept towards source code management
which isn't that easy to grasp. But there are lots of tools,
documentation and hints available to make this step as easy as possible.

Comments anyone ?

But that's not a system solution. After all, I'm fixin' just an error in UI,
what the heck do I need sat-solver for? So, either I'm doing something wrong
or something is rotten in the state of Denmark ...

Well, actually both.
You can do the bugfix by branching off an earlier revision of libzypp
(before sat-solver, e.g. just immediately after 10.3) and merge it back
after testing.
For the general case, see above.


[...]
Anyway, I'm speaking up and raising the topic :)

Good, thank you !

Klaus
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References