https://bugzilla.novell.com/show_bug.cgi?id=439538
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=439538#c1
Danny Kukawka changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #1 from Danny Kukawka 2008-10-29 11:09:11 MDT ---
We put them together into one package because we don't update hal-info without
HAL since one (can) depend and break the other due to e.g. changes or fixes of
properties, devices, fdi-rules etc. Since we have to do Q&A/Testing both
packages for each update it make no sense to split them up. There is for us as
distributor no advatage of split up the packages, it don't make anything esier,
also because HAL won't wont work correctly because hal-info and vice versa.
Btw. IMO the text/advice of the HAL website isn't true. There where already
problems in the past with the bilateral dependencies between particular version
of both.
Only one example why it's not possible to have 'always the latest hal-info' for
openSUSE users: the latest hal-info depends on the latest hal git version. If
there get something new introduced (new devices, changes in the device tree,
new FDI directives or rules) which isn't part of the in our product released
HAL version it would break the existing installation if you install the latest
hal-info over/to an older HAL release.
For me as maintainer of the package (and also a upstream developer) it's much
easier to handle both in one since I can guarantee that everything work
together in the correct way in our products.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.