Reply To: To modernize antiX or …

Forum › Forums › antiX-development › Graphics › To modernize antiX or … › Reply To: To modernize antiX or …

#23356
Anonymous

    Here’s a quickstart workflow for creating a local copy of the “antix-goodies” project, and uploading (pushing) your changes back to the gitlab-hosted project repository after having locally edited of one or several of the project files.

    sudo apt install git (prerequisite)

    git clone http://gitlab.com/antix-contribs/antix-goodies
    ^—> this will create a subdirectory in the current working directory and download the remotely-hosted files into it.
    It’s probably desirable to cd ~/directory_of_your_choice prior to issuing the “git clone” command.
    Also, if you intend to clone multiple projects, makes sense to create a parent holding pen directory
    e.g. “gitz”, and cd ~/gitz prior to issuing a “git clone …” command

    Browse to the newly-created directory using a gui file manager, and view the content of its “bin” subdirectory.
    While reading this turorial, take a peek here: http://gitlab.com/antix-contribs/antix-goodies/tree/master/bin
    When you upload (push) changed files, this is where they they will reside in the remote project repository. Eventually, after the project files have been packed into a .deb file, redistributed via antiX repo… when installed via sudo apt [..]
    they will be installed to /usr/local/bin/
    ^—> This detail, “/bin within the project sourcefile tree” matches the eventual destination “/usr/local/bin/”, is specific to the antix-goodies package. (FYI, for any given package, mapping rules are usually stated within the package’s debian/rules file).

    Because the “rules” file often does not specify the intended (correct, required) set of permissions for each packaged file, you should (and a maintainer MUST) verify that each to-be-packaged file bears correct permissions.
    .

    After editing one of the existing antix-goodies scripts and/or drag-n-dropping your additional script files into the “bin” directory:

    git add *
    ^—> This command (more or less) “freshens the file manifest” of your local project.

    When you are ready to upload (push) the changed project files back to the remote git(lab) repository:

    git push http://gitlab.com/antix-contribs/antix-goodies
    ^—> This command will prompt you to type your gitlab.com username//password,
    and a (60 char or less) “commit message” describing your changes.

    (You can, optionally, instruct git to store your login credentials globally, er, permanently
    in order to avoid the prompt during each push transaction.)

    Blip. Done.
    Immediately following completion of a push operation, the changed files are accessible worldwide from the gitlab.com -hosted project repository.
    (to verify, you can check via web browser) http://gitlab.com/antix-contribs/antix-goodies/tree/master/bin