https://bugzilla.redhat.com/show_bug.cgi?id=1824467
--- Comment #8 from Till Hofmann <[email protected]> --- Thank you for reviewing! (In reply to Alexander Ploumistos from comment #5) > While we're waiting for the scratch build to complete to wrap up the review, > I have a couple of questions. > > Do you intend to package the python bindings at a later time or not at all? > I know in which cases we are required by the packaging guidelines to remove > stuff from a source tarball, but are features like that elective? I don't think there is any guideline that says that you need to build all features of a package. Usually, I add them if I need them or if someone requests them. It also depends on how much work is needed. That being said, I'll look into building the bindings for freeopcua. > > I know how push and pop are used in Perl arrays, but I've never understood > how they work in a spec file and what their purpose is; if the explanation > won't take up too much of your time, could you please explain how it works? It's quite simple actually. `pushd dir` is like `cd dir`, except that it remember the directory you came from and pushed it onto a stack. `popd` pops from the stack and `cd`s into the first item of the stack. Using pushd/popd here is not really necessary, I just got used to it, because it allows switching directories in a script without getting lost. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
