Changes between Version 8 and Version 9 of WikiStart


Ignore:
Timestamp:
30/10/10 18:51:28 (9 years ago)
Author:
dlove
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v8 v9  
    77[http://www.gnu.org/philosophy/free-sw.html free software] project,
    88now that Oracle have taken it over, are not contributing their source, and
    9 may well close down the Sunsource web site.
     9may close down the Sunsource web site.
    1010
    11 The idea is to encourage sharing, in the original spirit of the
    12 project and on the basis of long experience of free software projects
     11The idea is to encourage sharing, in the spirit of the original
     12project and informed by long experience of free software projects
    1313and scientific computing support.  Please contribute and share any
    14 ideas for improvement, especially for encouraging contributions.
     14ideas for improvement, especially ideas for encouraging contributions.
    1515
    16 As long as it's there, look at the
     16As long as it's there, you can look at the
    1717[http://gridengine.sunsource.net old gridengine site]
    1818for extra documentation etc.  Currently anything
     
    2929actually only goes back to the `V60` tag—i.e. not including
    3030version 5.3—and also has some re-buildable files removed, to keep it a bit more
    31 manageable.  Note that only the repository trunk was converted for each
    32 repository.
     31manageable.  Note that only the trunk of repository trunk was converted.
    3332
    34 These are currently just available via [http://darcs.net/ darcs], but
    35 should be mirrored, at least to Mercurial, eventually.  Darcs is a
     33These are currently just available under [http://darcs.net/ darcs], but
     34are intended to be mirrored eventually, at least to Mercurial.  Darcs is a
    3635nice distributed version control system, but doesn't currently scale
    37 too well with a repository of this size and age.  It's fine for
     36so well with a repository of this size and age.  It's fine for
    3837looking at the change history and recording new changes, but currently
    3938slow at producing diffs for previous changes, for instance.
     
    6362* HTML documentation: This is either rebuild-able (like Javadocs) and/or probably not useful outside the gridengine web site (like HTML-ized man pages).
    6463
    65 === History ===
     64== Building ==
     65
     66Building the source is currently rather a pain,
     67which is something to improve urgently.  With appropriate development
     68packages installed—they need documenting—it should build on GNU/Linux
     69with something like
     70{{{
     71cd source
     72./aimk -only-depend && scripts/zerodepend && ./aimk depend &&
     73./aimk -system-libs -no-gui-inst
     74}}}
     75
     76== Bug reporting, patches, and mail lists ==
     77
     78There aren't currently any accessible mail lists associated with the
     79project, but should be soon, and unfortunately you can't currently reply to
     80any mail from the tracker, such as notifications of tickets.  You can create an account
     81to put tickets in the [ticket: issue tracker], or use the `tourist`
     82account with `sge` as the password.  If you do use tourist, it may be useful
     83to put a mail address in the report in case of queries.  (It will eventually be
     84possible to make bug reports by mail.)
     85
     86The best way to send patches is to record them in your local darcs
     87repository and use `darcs send`.  Until arrangements are made for
     88direct contributions, they will be pushed into the main repository by
     89hand if they look reasonable.  You could also just mail (see
     90[#contact Contact]) normal patches, maybe even against the 6.2u5
     91source, if you have any already, or attach them to a ticket.
     92
     93If you record changes with darcs, make the patch name a useful short
     94summary of the patch, and include the number of any ticket it fixes in
     95the form {{{fix #}}}//N//, where //N// is the ticket number.  If it
     96also refers to an item //N// in the sunsource Issuezilla system, it's
     97useful to include that also in the form IZ//N// even though the
     98imported tickets have that reference.
     99
     100== History ==
    66101
    67102The original CVS repo is currently still
    68 available if you need more history, and has been backed up in case it
     103available if you need more history, and has been mirrored in case it
    69104disappears, along with copies of items in the
    70105[http://gridengine.sunsource.net/servlets/ProjectIssues issue-tracker]
     
    93128[http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence]
    94129except for some essentially ‘third party’ stuff like `qmake`.
    95 
    96 == Building ==
    97 
    98 Building the source is currently a pain,
    99 which is something to improve urgently.  With appropriate development
    100 packages installed—they need documenting—it should build on GNU/Linux
    101 with something like
    102 {{{
    103 cd source
    104 ./aimk -only-depend && scripts/zerodepend && ./aimk depend &&
    105 ./aimk -system-libs -no-gui-inst
    106 }}}
    107 
    108 == Bug reporting, patches, and mail lists ==
    109 
    110 There aren't currently any accessible mail lists associated with the
    111 project, but should be soon.  Note that you can't currently reply to
    112 any mail, such as notifications of tickets.  You can create an account
    113 to put tickets in the [ticket: issue tracker], or use the `tourist`
    114 account with `sge` as the password.  (It will eventually be possible
    115 to make bug reports by mail.)
    116 
    117 The best way to send patches is to record them in your local darcs
    118 repository and use `darcs send`.  Until arrangements can be made for
    119 direct contributions, they will be pushed into the main repository by
    120 hand if they look reasonable.  You could also just mail (see
    121 [#contact Contact]) normal patches, maybe even against the 6.2u5
    122 source, if you have any already, or attach them to a ticket.
    123 
    124 If you record changes with darcs, make the patch name a useful short
    125 summary of the patch, and include the number of any ticket it fixes in
    126 the form {{{fix #}}}//N//, where //N// is the ticket number.  If it
    127 also refers to an item //N// in the sunsource Issuezilla system, it's
    128 useful to include that also in the form IZ//N// even though the
    129 imported tickets have that reference.
    130 
    131 When reviewing tickets imported from Issuezilla, note that any
    132 hyperlinks appearing in the main description are bogus unless they are
    133 normal URLs, and some of the tickets have the summary messed up due to
    134 the way they were imported, which is probably not worth fixing now.
    135130
    136131== Related ==