× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi John,

I am only knowledgeable enough to recognize that the comments are too old,
not to suggest proper ones.

As best I can tell the README.md is accurate and up to date. Maybe it
would be good to further explain how the .lst files work. There are cases
where you'd want a specific version of a given package and by having, and
keeping, multiple versions for, say, git, we are able to allow people
flexibility. The alternative would be to have only one pkg_perzl_git.lst
and always having it contain the latest and not support the install of
older versions.

We ~could~ make it more like apt-get or other by making the pkg_setup.sh
script much more refined, but at the end of the day the perzl stuff will
just be a stepping stone until we formally adopt (and build) something
better (i.e. a full fledged package manager).


Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Sep 1, 2016 at 12:07 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

[Was: See all IBMiOSS RFEs]

On Thu, Sep 1, 2016 at 12:12 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
[John Y.:]
And wandering even further off topic, just how old
is that README.md (that comes with Option 3)?
Those comments next to the .lst files (for perzl
versions of gcc, perl, and python) are quite obsolete.

How far off is it from the repo's current README.md?
http://bit.ly/2ccfFr8

That text hasn't changed.

Pull Requests are welcome :-)

I apologize for playing the role of complainer, but in this case I am
only knowledgeable enough to recognize that the comments are too old,
not to suggest proper ones.

I also recognize that both temperament (extreme conservatism) and
resource constraints contribute to packages and even operating systems
being out of date. (Witness all the folks still running V5R4, for
example.) I know we have a Red Hat box in production where I work,
whose system Python is version 2.3.something. Just insanely ancient.

Given that the listed perzl versions may be the latest available (with
little to no prospect of newer ones any time soon), maybe the old
comments are the most appropriate ones after all? As new things show
up from IBM or the community, that new stuff should naturally
supersede the perzl stuff, comments and all.

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.