pkg_perzl_git-1.8.5.4.lst relpication and duplication needs fix?

Issue #7 resolved
Former user created an issue

pkg_perzl_git-1.8.5.4.lst

Why mutiple versions of the same RPM loaded?

Why not include causually related functions like bash ifn other :file(s)?

Comments (6)

  1. Aaron Bartell

    Why mutiple versions of the same RPM loaded?

    I originally followed the perzl .deps to a 'T' and wasn't sure if multiple versions were required for some things (NOTE: Some of the rpm installs allow multiple versions and some don't).

    I've since de-duped.

    Why not include causually related functions like bash ifn other :file(s)?

    Do you mean have a pkg_perzl_bash-x.x.x.lst file and then use it in pkg_perzl_git-1.8.5.4.lst in the :file section? If so, yes, that sounds like a good idea since bash will most likely be a common independently-installed rpm. We could/should also create one for zsh given the Node REPL issue with bash.

  2. Former user Account Deleted reporter

    Correct, subset(s) chroot_xxx.lst 'common utilities', allows for easy combinations of bigger download/intsall tasks (aka, gcc compile environ wants bash, git wants a bash, etc.). All using :file to simply include nice to have stuff.

  3. Aaron Bartell

    Sounds good. Let's take that approach. I will fix pkg_perzl_git...lst and create a pkg_perzl_bash....lst.

  4. Former user Account Deleted reporter

    I have pkg_perzl_utils.lst, which has many of basic utilities any project needs. Check it out, see if it can server you needs as well (i did not add joe yet for instance).

  5. Aaron Bartell

    I have pkg_perzl_utils.lst, which has many of basic utilities any project needs. Check it out, see if it can server you needs as well (i did not add joe yet for instance).

    Just got done using/testing it. I added a :file for bash inclusion and it is working. Learned the hard way you need two blank lines at the end of the *.lst files - one for git and one for pkg_setup.sh processing (lost an hour on that one).

    I am marking this issue as resolved.

  6. Log in to comment