Although Greg is currently majorly refactoring it, the normal way of contributing would be to send a PR (pull request/merge request) to https://github.com/gnustep/tools-scripts. Greg could then review it and either request changes or merge it.
On Fri, Mar 14, 2025, 20:20 Steven <[email protected]> wrote: > Hi Everyone, > > I’ve been reading through the gnustep-discuss thread "GNUstep Public > Relations" and this is something I would like to help with if there’s a > need. I’m wondering if there’s a published plan or a set of goals the > project is working towards and interested parties could take on the task? > > I’ve been following GNUstep off and on for a long time and I’m just > re-familiarizing myself with everything. I just gave the > gnustep-web-install-dev script a try as per the instructions on > gnustep.org but unfortunately it didn’t work. After displaying the ascii > art I got: > > > IMPORTANT! > You must update your .ssh directory so it contains your github ssh key > Begin setup for linux > bash: line 45: ./setup-linux: Permission denied > ======== Create gnustep build directories ======== > Cloning into 'tools-scripts'... > The authenticity of host 'github.com (140.82.112.4)' can't be established. > ED25519 key fingerprint is > SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This key is not known by any other names > Are you sure you want to continue connecting (yes/no/[fingerprint])? yes > Warning: Permanently added 'github.com' (ED25519) to the list of known > hosts. > [email protected]: Permission denied (publickey). > fatal: Could not read from remote repository. > ... > > After this I tried out the slightly different script/instruction shown on > gnustep.github.io site (gnustep-web-install) > This one worked a bit better for me: > > Begin setup for linux > ./setup-linux: line 7: /etc/lsb-release: No such file or directory > sudo command is already present. > Checking if root password is not set, please set it... > Adding steven to sudoers... > Please enter the root user's password. > Password: su: Authentication token manipulation error > ======== Create gnustep build directories ======== > Cloning into 'tools-scripts’… > > That error show shown in setup-linux line 7 is because I am running > Slackware, which does not have /etc/lsb-release but it does have > /etc/os-release > Having said that I would like to work on a > “install-dependencies-slackware” script and maybe fix up the > gnustep-web-install script to cater for Slackware also. > > I don’t know how to go about contributing changes or documentation or > anything else like that, is there a process? > Do changes get reviewed by someone? > > The other issue I did have with the gnustep-web-install script is the post > installation failed: > > ... > GNUmakefile:31: Unable to obtain GNUSTEP_MAKEFILES setting from > gnustep-config! > … > > Once I manually fixed up my path, the post-install-linux script runs, but > it fails because it can’t link Gorm with libdispatch. Taking a closer look > I see that it is built as part of gnustep-web-install but is installed > in /usr/GNUstep/System/Library/Libraries/libdispatch.so which is not in > ld’s path. I created /etc/ld.so.conf.d/gnustep.conf containing the path, > ran ldconfig and the post install linking completed. > > So the good news is there’s only a few things to fix and Slackware could > be listed as a GNUstep target system! > > My other observation I have is, right at the start of the script is says > it’s adding my user to sudoers (it’s already a sudoer) but also prompts for > the root password, is that necessary? > > > Cheers > Steven > > > > > > >
