| alan_g | xnox: after your comments on my using an epoch, can I get your thoughts on my attempt to avoid it? (I'm not confident of my debian incantations) https://code.launchpad.net/~alan-griffiths/mir/move-miral-to-mir-no-more-miral-packages/+merge/329993 | 13:24 |
|---|---|---|
| xnox | alan_g, let me tell you a secret =) | 13:27 |
| xnox | alan_g, binary package version number, may not match source package version numbers =) | 13:27 |
| alan_g | xnox: tell me more | 13:28 |
| xnox | alan_g, ideally you should keep libmiral binary packages, as each shared library, ideally, should be shipped in a stand alone package (e.g. like src:boost1.64 ships gazillion libboost*foo packages) | 13:28 |
| xnox | alan_g, and you can specify override_dh_ commands with -p options to set particular version numbers for some packages | 13:28 |
| xnox | e.g. let me find an example | 13:28 |
| xnox | such that e.g. src:mir generates libmir1 at 1.0.0 yet libmiral at 1.5.0 | 13:29 |
| xnox | etc. | 13:29 |
| alan_g | There is really only libmiral that it makes sense to keep | 13:29 |
| xnox | but one has to be careful to derive the version numbers right, such that they are based on debian/changelog and increment | 13:29 |
| xnox | alan_g, yeap exmaples, binaries, dev can all go, but libmiral1 or what not is useful to have | 13:29 |
| xnox | alan_g, i have a call, but i will review and get back to you! | 13:30 |
| alan_g | xnox: great! thanks | 13:30 |
| === JanC_ is now known as JanC | ||
| alan_g | xnox: did you find an example? | 15:29 |
| xnox | alan_g, i'm still in meetings =) | 15:30 |
| alan_g | xnox: np. | 15:30 |
| === chihchun_afk is now known as chihchun | ||
| === chihchun_afk is now known as chihchun | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!