IRC log for #gooseproject on 20130111

15:58.37shalkieGoOSe Morning
15:58.53shalkieBig White Fluffly snowflakes everwhere.
16:23.52*** join/#gooseproject figg3 (~figg3@c-7719e455.015-382-73746f7.cust.bredbandsbolaget.se)
17:14.13herloQuite a snowy GoOSe morning!
17:15.16shalkies/fly/fy/
17:15.38shalkieherlo: Yeah, are you going to brave the high "alta"tude today? ;-)
17:16.11herlonope, sick
17:16.31herlohoping to be better enough to go tomorrow or sunday though
17:17.06shalkieI see.
17:17.17herloshalkie: I think we're really close to a GoOSe release too. I might just work on it this weekend between moving the last stuff from our old place.
17:18.23herloshalkie: mostly just a cough and chest congestion. If I don't feel well enough to ski, I'll be here, GoOSing!
17:18.58shalkieHah! I am more surprised you don't have some clever way of GoOSeing while riding the ski lift.
17:19.08shalkieSorry to hea ryour sick.
17:19.20shalkies/ ry/r y/
17:25.50herloshalkie: thanks. I'm hoping to kick it today
18:56.17zoglesbyanyone know of a way to define a %post in a spec that will not run on OS install?
18:57.08herlozoglesby: what is the purpose?
18:58.26zoglesbyherlo: we have some custome rpms at work that have %post sections to configure them. I want to add them to the install iso, but I don't want to run the config script
18:58.54zoglesby/s/custome/custom
18:59.14herlozoglesby: oh, you mean they are interactive?
18:59.24zoglesbyherlo: yeah
18:59.54herlozoglesby: one thought would be to alter the post section to read a config file you drop in place, rather than being interactive. It's a set rule that rpm is supposed to be non-interactive.
19:00.11herloafaik, you probably would have to interact with each install otherwise.
19:00.17herlowhich sounds completely lame
19:01.02herlozoglesby: one way though would be to download the rpm, do rpm2cpio and copy it to the right locations
19:01.19herlobut that seems like it's defeating the purpose of rpm altogether
19:07.40goozbachyou could do some logic in your %post to cat /proc/cmdline or something and have it not execute if inside of anaconda
19:08.00goozbachnot sure that /proc/cmdline is the right file, but the idea is sound
19:08.23goozbachbut the more correct answer is to remove the interactivy from your rpm.
19:08.38goozbachbreaks the speification
19:08.52zoglesbyherlo: I did not want to have interactivity in the rpm, but lazy admins won that fight
19:09.35herlozoglesby: can you just rewrite the post section to include a way to use defaults and change them after the fact?
19:09.44herlopost in kickstart, that is
19:10.05herloexpect would work, though it's annoyingly painful
19:10.34herloor rewrite the rpm to assume certain defaults if no input is provided in X seconds (like 10)
19:13.32zoglesbyI don't like any of the options (but thank you both). I am just going to try and fight with ops about this again.
19:13.48herlozoglesby: do you not have control of the srpm? :D
19:14.15zoglesbyherlo: I have all the control, I am the only one who knows how to do any of this
19:14.36herlozoglesby: then just do it your way
19:14.55zoglesbyherlo: "But with the old process......"
19:14.57herlotell them that interactive isn't going to work due to constraints of the automated installation
20:00.13shalkieOr in a worst case scenario just tell them "Yes, that was the old way... This is the modern way."
20:00.23shalkieducks behind the couch
20:03.19shalkieIs there a way to specify rpm options to anaconda? Cause there are options like --noscripts for rpm. I just don't know how you would tell anaconda that.
20:03.58herloonly in a kickstart
20:04.45herlobut doing --noscripts is probably not what zoglesby wants, since I would think he wants some pre/post script stuff to happen, just not interactively.
20:50.14zoglesbyNo matter, I pulled out the documentation and told them I would not support it
20:50.20zoglesbyend of story
20:51.28herlohehe
22:58.54shalkie:-)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.