-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
split manual 76.2.1 into two subsections #1877
Conversation
By the way, are there really any packages which do the following? |
Codecov Report
@@ Coverage Diff @@
## master #1877 +/- ##
==========================================
+ Coverage 63.63% 63.69% +0.05%
==========================================
Files 946 946
Lines 283525 284388 +863
Branches 12686 12746 +60
==========================================
+ Hits 180426 181136 +710
- Misses 100313 100455 +142
- Partials 2786 2797 +11
|
@cdwensley thanks indeed, looks like in former times there was the
Many packages still have that components which is now likely ignored. This should be checked and then the documentation may be updated as appropriate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some comments, but none of them are requirements, if you disagree with them.
doc/ref/gappkg.xml
Outdated
⪆ distribution already contains all currently redistributed with | ||
&GAP; packages in the <F>&GAPDIRNAME;/pkg</F> directory. | ||
The &GAP; distribution contains, in the <F>&GAPDIRNAME;/pkg</F> | ||
directory, all currently available &GAP; packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
available -> redistributed I think (there are packages not distributed with GAP)
doc/ref/gappkg.xml
Outdated
your &GAP; installation and calling the <C>../bin/BuildPackages.sh</C> script. | ||
Before a package can be used it must be installed. | ||
A standard distribution of &GAP; already contains all the packages | ||
currently available with &GAP;. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, maybe currently redistributed
doc/ref/gappkg.xml
Outdated
be able to use some or all external binaries. | ||
&GAP; root directories (see <Ref Sect="GAP Root Directories"/>). | ||
If you don't have access to the <F>pkg</F> directory in your main &GAP; installation you can add private root directories as explained in that section. | ||
<P/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe say in section <Ref Sect="GAP Root Directories"/>
, to make clear what "that section" is.
lib/package.gd
Outdated
## (see <Ref Func="CompareVersionNumbers"/>). | ||
## The argument <A>name</A> is case insensitive. | ||
## If the first character is <C>=</C> then only that version will be loaded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... first character of version is ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your comments - I now need some git advice.
Before doing any of the suggested editing I did the following:
(1) in master, did: git pull upstream master, then git push origin
(2) git checkout manual76again, then git rebase master
(3) attempted git push origin manual76again , but got error message:
"error: failed to push some refs to 'https://github.com/cdwensley/gap'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart." etc.
Looks like I've made another mess of things? Any suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whenever you perform a rebase, you will have to add --force
to the git push after that.
In general my advice would be to not worry about rebasing and merging master in -- unless your commit interferes with anyone else, it's fine to drift behind slightly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cdwensley - glad that this gets more attention, and like how you reduced duplications. Made some suggestions.
doc/ref/gappkg.xml
Outdated
<P/> | ||
&GAP; packages are written by (groups of) &GAP; users which may not | ||
&GAP; packages are written by (groups of) &GAP; users who may not | ||
be members of the &GAP; developer team. The responsibility and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd insert "necessarily" between "may not" and "be members"
doc/ref/gappkg.xml
Outdated
process. | ||
The &GAP; development team will assist in making any new package | ||
suitable for distribution with &GAP;. | ||
It is possible to submit a package to a formal refereeing process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is possible -> It is also possible
doc/ref/gappkg.xml
Outdated
&GAP; root directories (see <Ref Sect="GAP Root Directories"/>). | ||
If you don't have access to the <F>pkg</F> directory in your main &GAP; installation you can add private root directories as explained in that section. | ||
<P/> | ||
Whenever you download an archive of a &GAP; package, it will contain a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of course, you can clone a repository instead of downloading, and a package which is mot redistributed with GAP may accidentally not have README (or README.txt or README.md) at all...
lib/package.gd
Outdated
## suppressed by using the <C>-A</C> command line option | ||
## (see <Ref Sect="Command Line Options" />). | ||
## <P/> | ||
## A &GAP; package may also automatically install just its documentation, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirm here looking at https://github.com/gap-system/gap/blob/master/lib/package.gi that now we call LoadPackageDocumentation
for all not loaded packages, so this should be rewritten accordingly.
(We may update ValidatePackageInfo
to show warnings for obsolete components).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After deleting this paragraph added, to the second paragraph of Ch.76, "(When &GAP; is started, LoadPackageDocumentation is called for all packages.)". Note that LoadPackageDocumentation is not currently in the reference manual, but that there is XML text for it starting at line 662 of package.gd.
d3544b4
to
d1274ec
Compare
Make all requested changes, but see comment above concerning LoadPackageDocumentation. |
@cdwensley if we are not going to document |
Seems ready now to be merged. |
@cdwensley Thanks. Who will be merging this, perhaps squash it into one commit. |
This PR started out as a comment on #484 (adding guidelines for package authors from Example package). It replaces the attempt which went badly wrong yesterday. It makes changes to sections 76.1 and 76.2 of the reference manual: (a) splitting the LoadPackage section in two, with a separate subsection on automatic loading; (b) removes some duplication; (c) rephrases some passages.