Bug 2041941

Hi Tomas,

Any update here ?

Regards,
Xavier

Hi Xavier,

Sorry about the delay, it totally passed through me to give an update here.

After further discussion and capacity analysis we agreed to move with python packages only (https://bugzilla.redhat.com/show_bug.cgi?id=1888195) but prior to do that we need to extend lasso gating tests (https://bugzilla.redhat.com/show_bug.cgi?id=2032652), so you might expect it in place in the near future.

Unfortunately, as you already stated, you are interested in perl bindings but it won't make it.

With that being said we are closing this BZ, if you disagree with the decision please feel free to reopen it.

Thank you for understanding
Red Hat Enterprise Linux Identity Management Team

I'm glad for the python folks, but the software I need this for is perl based. The need for python binding was just a wild guess, and it was correct.
Not shipping the perl bindings makes the whole lasso package unsuitable to my use case, so indeed I disagree, but I have no say in the matter. So much for the (unpaid) time I spent cleaning up and fixing the lasso specfile, including, indeed, producing a proper perl bindings sub-package (check the specfile commits). I'll have to either rebuild my own or make a lasso-epel package shipping the missing perl bindings. The former is easy, but doesn't benefit the community. The latter is yet more unpaid work for me, and in the end, mostly benefit Red Hat, so why should I bother, as I won't be returned the favor ?
Not shipping all built sub-packages, including -devel, makes it more and more difficult and cumbersome to support RHEL and a way less appealing platform.

Any chance this decision gets examined again ?
The package I need this for is now available in Fedora, where the lasso perl bindings are available and thus is full-featured. Said package is also available in EPEL, but without SAML support.
As I already wrote, the alternative is a lasso-epel package, which provides only the perl bindings sub-package, but creating and maintaining such a package doesn't look like a useful use of time, while I have already done all the work to have a useful perl bindings sub-package, as well as quite a bit of overall cleanup of the package (and I just filed yet another cleanup PR against lasso).

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.