Thanks William... > If you mean what libraries are included in an official release, you > would download the release and look at what files are included.
How long will it take for someone to check? > If you mean what libraries are planned for next release, those files > are in TORELEASE. A bit inconvenient. We currently just use whichever is newest. Another issue is that the user will not know if they are using an old file. When I upgrade my libs, I just copy/paste over what is already there. If the old file name is the same and the new one is different, I'll still be using the old one without knowing there is a new one. It has to be obvious which file they should be using. The person that creates the package can name files however they wish, and include whatever files they wish. > But if you want to make it obvious, you could > for example have a subdirectory named 'forks', 'experimental', or > 'rfc', or 'proposed', or some such. In this case, the older library would get more attention then the new library. Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
