[04:47] hey guys [06:15] Unit193: looks like jbicha already did it [07:33] Yep, so I saw. === shadeslayer_ is now known as shadeslayer [19:23] hi all [19:23] i had a question about a philosophy wrt packaging [19:24] could the upstream Makefile build the source and create modules (executables, libraries, modules, etc.) but not "install" it [19:24] and the packaging take care of installing it? [19:24] so the upstream might have a readme about how you "could" install it [19:24] but wouldnt do it for you [19:25] i already have some debian packages that are in xenial and trusty (thank you profusely) [19:26] but im thinking of changing them so the upstream (building) and packaging (installing) are separate as well as adding a new package which really lends itself to that philosophy [21:05] karstensrage: that's basically how debian/rules works already, no? === acheronUK is now known as acheronuk === grumble is now known as grumble2 === grumble2 is now known as grumble [22:59] rbasak, i thought maybe the packaging used the upstream to figure out how to install things [23:30] karstensrage: ah. Yes, usually it does. You can override that though. [23:42] ok so if i changed how en existing package works due to changing upstream [23:42] is that ok [23:42] ?