Hi All, I want to provide a little more general information on FDVCS for those that are not familiar.
- It is not required to use the tool to clone a project. It gets its information from GIT. So, there is not anything it requires to be done when working with a project. I do recommend using the “-s” option to fix timestamps on your local files if you used git directly to clone the project. - When the utility is told to clone a project, it fetches a CSV file from download/update package repository on IBIBLIO (by default) that is maintained by the Repository Management Utilities (fdrepo). That CSV contains a list of all current projects and their group information. FDVCS uses the information in that CSV to locate the source packages In the FreeDOS GitLab Archive. - SSH Keys or HTTPS. FDVCS defaults to using SSH Keys. But, if you don’t have that setup, you can tell it to use HTTPS. This behavior can be override permanently in a settings file for FDVCS. Depending on the remote projects settings on the server, a project that is cloned using https may not be able to push changes back to the server. This is a Git/Server issue not an issue with FDVCS. I considered just having FDVCS fall back to cloning projects HTTPS if SSH failed. But because of the complications that can occur when using HTTPS, I opted to not have the utility do that automatically. - The settings.cfg is not required for FDVCS normally. If you use the tool to clone the FD-NLS project to work with translations or update translations in projects, the utility will create the settings file to store the location of the local copy of FD-NLS. - You can also use git directly to commit and push changes. But, when doing that you will need to use the “fdvcs3.sh -s” option to update the timestamp information. Also, if the project LSM metadata has changed you will want to update the INDEX.md file in the project root by using “fdvcs3.sh -cpr”. Or, simply do both at the same time using “fdvcs3.sh -cpr -s”. But honestly, it is much easier to simply use the ‘-c message’ option and let let the utility figure out what (if anything) needs done. - The settings file can also be used to override a number of built-in default settings: # Don’t mess with this setting… It is the user/base project used for SSH checkout of projects on GitLab. REPO_USER="g...@gitlab.com:FreeDOS" # Base URL for fetching GitLab projects over HTTPS URL_GIT="https://gitlab.com/FreeDOS” # URL for cloning the FD-NLS project URL_NLS="https://github.com/shidel/fd-nls.git” # URL for the Download/Update repository package information CSV URL_CSV="https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/listing.csv"; # Projects that FDVCS should not try and integrate NLS translations. # LSM Metadata is standardized and can be performed on all packages. NLS_SPECIAL=";htmlhelp;blocek;fdtui;imgedit;blkdrop;sayswho;" # Not set by default. On macOS, it will try to use Safari. On Linux, it will try to use FireFox. unset BROWSER # Will be set automatically if FDVCS is used to clone the FD-NLS project. unset FDNLS_DIR # Display a lot of other messages when processing unset VERBOSE_MODE # Be very quite, but still show warnings and errors unset QUITE_MODE # Always use HTTPS instead of SSH for GitLab. unset HTTPS_MODE There are other things. But, this is enough for now. :-) Jerome
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
