Bug 614287 - More information is necessary in 3.1. Compatibility
Summary: More information is necessary in 3.1. Compatibility
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Developer_Guide (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: Don Domingo
QA Contact: ecs-bugs
Keywords: Documentation
Depends On: 642395 642397 642399
TreeView+ depends on / blocked
Reported: 2010-07-14 03:00 UTC by Masahiro Ito
Modified: 2011-12-07 02:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-12-07 02:31:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
draft build of RHEL6 Developer Guide (as of October 27, 1010) (2.34 MB, application/x-pdf)
2010-10-07 04:28 UTC, Don Domingo
no flags Details

Description Masahiro Ito 2010-07-14 03:00:52 UTC
Description of problem:

In the section 3.1. Compatibility, the list of core libraries
doesn't seem user-friendly.

* Can you specify if they are filenames, or RPM package name.
  For example, at first glance, it's not clear if "libc" means only
  libc.so.6 or glibc RPM package. If you specify the form (either
  filename or RPM package name), you can define the range of core
  library clearly.

* Can you write in the format of full name? Some library names are shortened.
  For example, it seems that "libgtk-x11-2.0" or "libgtk-x11-2.0.so.0" are
  better than just "libgtk", because you can identify a library file easily
  and clearly.

* We need compat-* library information.
  When running application from older RHEL version, we need some
  compat-* libraries such as compat-glibc, compat-libstdc++, and so on.
  Can you add description like this?

    When you run RHEL 5 applications on RHEL 6, you might need:

    When you run RHEL 4 applications on RHEL 6, you might need:

Version-Release number of selected component (if applicable):

Developer Guide, published on http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/ at June 2010

Revision 1.0 Thu Oct 08 2009

Actual results:

Expected results:

Additional info:

Comment 3 Benjamin Kosnik 2010-09-30 16:02:30 UTC
Hey. I re-did this based on the comments, added Package Names and added a RHEL 4 column. This draft is more coherent, I think. Please look at this and give more feedback.

Comment 4 Masahiro Ito 2010-10-07 04:12:58 UTC

Thanks for letting me know that, but I can't see the up-to-date version with this site.


Correct me if I'm wrong, but I guess the latest is available only in Red Hat. Or should I access with another URL for the latest one?

Comment 5 Don Domingo 2010-10-07 04:28:05 UTC
Created attachment 452033 [details]
draft build of RHEL6 Developer Guide (as of October 27, 1010)

Hi Masahiro,

sorry about that. attached is a draft build of the document in PDF format. it should contain all the changes mentioned by Benjamin.

Comment 6 Masahiro Ito 2010-10-14 10:56:02 UTC
Hi Don and Benjamin, 

I checked Developer Guides improved much and it covers my feedback, but can I ask one more thing?

This might be a technical question rather than feedback on the document. I found there is compat-glibc RPM in RHEL 6 DVD, but according to Table 3.2. Core Library Compatibility (ABI level is 2), you don't need compat-* library for glibc. They look like inconsistent with each other, so I'm a bit confused.

Can I confirm if we need compat-glibc for running applications built on RHEL 4/5?

Comment 7 Don Domingo 2010-11-23 02:11:41 UTC
Benjamin, could you answer Masahiro's question?
for now, i'm setting this bug as MODIFIED.

Comment 9 Benjamin Kosnik 2011-03-24 10:11:03 UTC
I think this compat package is just for nss changes but I'm not entirely sure and in any case don't have access to my usual RHEL 6 vm at the moment to look at the rpm. I'll add Jakub and maybe he can clarify.

Note You need to log in before you can comment on or make changes to this bug.