Opened 16 years ago

Last modified 11 years ago

#247 new defect

IZ1613: existing values in scripts/ break staging for many people

Reported by: craffi Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0u4
Severity: Keywords: cleanup


[Imported from gridengine issuezilla]

        Issue #:      1613             Platform:     All      Reporter: craffi (craffi)
       Component:     gridengine          OS:        All
     Subcomponent:    cleanup          Version:      6.0u4       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
       * Summary:     existing values in scripts/ break staging for many people
   Status whiteboard:

     Issue 1613 blocks:
   Votes for issue 1613:

   Opened: Tue May 10 13:38:00 -0700 2005 

I'm not sure if this issue is best as a "doc" componant (clarify README.BUILD)
or perhaps it should be a "cleanup" componant so that scripts/ can
be corrected so that the offending settings that break people's staging attempts
can be commented out.

The main issue is this:

(1) README.BUILD does recommend that people read scripts/README.distinst for
more information about staging freshly built binaries for distribution.

What it DOES NOT mention, however, is that there are already values entered into
the site-specific file scripts/ that are almost certain to
break/halt anyone's attempt to actually use the dist script to build an SGE
tarball for distribution.

Either README.BUILD section (8) should be edited to clarify the fact that the
user should carefully check and alter scripts/ to make sure that
local settings are reflected


We should clean up scripts/ to comment out the following lines:

 # Base directory where the openssl binary and libraries reside

 # Base directory where BDB resides

... so that they do not affect users building tarballs from freshly built SGE

Change History (0)

Note: See TracTickets for help on using tickets.