> One of the problems with calling RPM, etc., true open-source project(s) is (a
> re) that there have been additions to make RPM work properly on Slack (for on
> e) suggested, and even written, but they have yet to become part of RPM prope
> r. Also, there are still some major problems with RPM and other package mana
> gers
"open source" and "code fork" are unrelated topics too. If different vendors
have there private versions, that's fine. They still have to supply source.
If they're sensible they will work with RH to get their changes incorporated -
otherwise they completely fork and look after their own, of constantly play
catchup.
And if they don't play the catchup games, their packages become as useful to
other users of rpm as debs, and vv.
--
Cheers
John Summerfield
http://www2.ami.com.au/ for OS/2 & linux information.
Configuration, networking, combined IBM ftpsites index.
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mail delivered to me is deemed to be intended for me, for my disposition.
