| 14:52.12 | *** join/#asterisk-doc newtonr (~newtonr@nat/digium/x-xkugosgmxvjppmlr) |
| 15:00.11 | *** join/#asterisk-doc blitzrage (~free-mads@c-174-62-142-83.hsd1.ma.comcast.net) |
| 15:01.28 | *** join/#asterisk-doc blitzrage (~free-mads@asterisk/documenteur-extraordinaire/blitzrage) |
| 15:01.28 | *** mode/#asterisk-doc [+o blitzrage] by ChanServ |
| 15:09.07 | *** join/#asterisk-doc leifmadsen (~free-mads@c-174-62-142-83.hsd1.ma.comcast.net) |
| 17:18.17 | *** join/#asterisk-doc leifmadsen (~free-mads@asterisk/documenteur-extraordinaire/blitzrage) |
| 17:18.17 | *** mode/#asterisk-doc [+o leifmadsen] by ChanServ |
| 17:22.07 | leifmadsen | jsmith: ping? |
| 17:57.21 | leifmadsen | jsmith: my question stems around RPM "management". Right now I have a single spec file for our custom build, and it covers 3 different minor versions of asterisk. I hate code duplication, but I think I'm "doing it wrong" this way. I feel like there should be a new spec file, and perhaps branch, for each version of Asterisk we're deploying |
| 17:57.36 | leifmadsen | do you have some understanding of how spec files and source patches, etc are managed? |