From Fedora Project Wiki

Looks pretty good. Afew comments:

  • Could ./ be put into a package?
  • Obtaining sources should also include copying over the the license file

--abadger1999 00:31, 22 April 2009 (UTC)

  • If the script should be put in a package (and I am not saying it should not), the most logical place is to put it in globus-core. So far the script has been a bit of a moving target, since it was regularly updated due to review comments, but it is stabilizing. If it is to be put in the distribution, a -help flag should be added, explaining the available options. If added, what is the right location for it: /usr/bin or /usr/share/globus? It might also make sense to drop the .pl suffix if the script is added to a package (especially if it is in the default PATH).
  • The source retrieval instructions has been updated (along with the examples and the script)
--Ellert 14:18, 23 April 2009 (UTC)
  • globus-core sounds fine. I'd put the script in /usr/bin. Dropping the suffix when installed sounds good too. Maybe change the name a little globus2spec, globus-spec-creator, globus-spec-gen, (if you're the upstream for the script).
  • Thanks for updating the source retrieval.
--abadger1999 15:01, 23 April 2009 (UTC)
  • The script is now installed as globus-spec-creator by the globus-core package.
--Ellert 15:49, 28 April 2009 (UTC)
  • Since there are so many globus packages that depend on each other, and almost all have a doc subpackage, should we consider putting dependencies among the doc packages? (Just an idea)

--oget 02:04, 22 April 2009 (UTC)

  • I don't think this is a good idea in general. If you want the docs for a high-level API, you normally don't want the docs for the low-level APIs the high-level API is built on. There are a few cases where there are inter-package links between HTML documentation (there are 2 packages like that). In this case it might make sense to depend on the package where the links point to. This is not implemented at the moment, but it can be added. This information is available in the GPT source package description file, so this dependency can be automatically added by the script (this information is already used to get the build dependencies right in this case).
--Ellert 14:18, 23 April 2009 (UTC)