RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 696189 - [RFE] Provide eclipse-photran package
Summary: [RFE] Provide eclipse-photran package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: distribution
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks: 607248 696190
TreeView+ depends on / blocked
 
Reported: 2011-04-13 14:06 UTC by J.H.M. Dassen (Ray)
Modified: 2018-11-14 13:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 696190 (view as bug list)
Environment:
Last Closed: 2011-12-08 16:14:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description J.H.M. Dassen (Ray) 2011-04-13 14:06:08 UTC
2. What is the nature and description of the request?

Include eclipse-photran fortran plugin http://www.eclipse.org/photran/

   3. Why does the customer need this? (List the business requirements here)

Needs to work on Fortran code in eclipse

   4. How would the customer like to achieve this? (List the functional
requirements here)

eclipse-photran is available via RHN or EPEL

   5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.

	yum install eclipse-photran

   6. Is there already an existing RFE upstream or in Red Hat bugzilla?

Couldn't find one

   7. How quickly does this need resolved? (desired target release)

5.8 if RHEL, asap if EPEL

   8. Does this request meet the RHEL Inclusion criteria (please review)

Yes

   9. List the affected packages

eclipse-photran

  10. Would the customer be able to assist in testing this functionality if implemented?

Yes

Comment 8 RHEL Program Management 2011-07-06 00:48:24 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 14 Siddharth Nagar 2011-12-08 16:14:15 UTC
We do not plan to include this package in RHEL. Looks like it is already present in EPEL and satisfies the customers' request. Closing.


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