Should tarball installations be supported?
Consider dropping tarball installations.
This should be discussed at the developers meeting after 3.4 release.
If tarball installations are still important, these should be checked.
e.g. A change was committed to master [13a3b1b2301dff5f385ae3a213c1b705ebaf28ca ] and is breaking tarball support in entry_q and antry_rm tools.
If tarball installations are mo more important, the documentation should be updated and all support removed
#6 Updated by Marco Mambelli over 1 year ago
All developers are in favor of dropping tar files distribution and installation.
Sent email to stakeholders:
Dear GlideinWMS stakeholders, currently GlideinWMS can be installed as RPM package and using tar files (with instructions to install and setup the required dependencies): http://glideinwms.fnal.gov/doc.prd/install.html We think that no user is currently using tar files based installations for the Factory and Frontend, so we'd like to drop the support for it. RPMs are much easier to install and we are supporting anyway only Red Hat based systems (that support RPMs). Please respond to this email before next Thursday 6/27 if you think file distributions support should be kept. If I don't hear back from anyone we'll plan on dropping tar files distribution support for the future releases. Thank you, Marco NOTE: this is only for Factory and Frontend installations. Glideins will still use tar files as they do now (e.g. to download and install in user space the HTCondor daemons). Nothing will change there