Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This isn't a good idea. Why? Because it takes IT from the position of being a roadblock, which is something you can push to get fixed and puts you in the wrong instead.

IT has valid reasons using RHEL and older packages, you presumably have valid reasons for using newer packages. If newer packages are needed work with IT to get those newer packages. This also means that they are back in the position of being a roadblock if critical projects really can't go forward due to their policies.

Sometimes the way to fix what is broken is to make your department stop being a crutch for failed IT policies.

Also, randomly changing system packages in production is a dick move. That sort of shit is (rightfully) going to result in getting your access revoked at the minimum.



Multiple hour long meetings with all of the internal authorities were involved. They all refused to allow new packages to be installed. Additionally, they were not even providing the proper update packages from RHEL due to system misconfiguration. EPEL was additionally forbidden. Regardless, the powers that be essentially said "You are not allowed to use the software that your project specification states that it needs."

It was either use other components or circumvent IT. The head of the department got fed up with the red tape and told us to circumvent. All proper discussion was done before that, and as a result nothing I did was a "dick move". The system was additionally not in production yet, so no changes in production were being done.

Shame on you for making too many assumptions.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: