| chatter29 | hey guys | 04:47 |
|---|---|---|
| Logan | Unit193: looks like jbicha already did it | 06:15 |
| Unit193 | Yep, so I saw. | 07:33 |
| === shadeslayer_ is now known as shadeslayer | ||
| karstensrage | hi all | 19:23 |
| karstensrage | i had a question about a philosophy wrt packaging | 19:23 |
| karstensrage | could the upstream Makefile build the source and create modules (executables, libraries, modules, etc.) but not "install" it | 19:24 |
| karstensrage | and the packaging take care of installing it? | 19:24 |
| karstensrage | so the upstream might have a readme about how you "could" install it | 19:24 |
| karstensrage | but wouldnt do it for you | 19:24 |
| karstensrage | i already have some debian packages that are in xenial and trusty (thank you profusely) | 19:25 |
| karstensrage | 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 | 19:26 |
| rbasak | karstensrage: that's basically how debian/rules works already, no? | 21:05 |
| === acheronUK is now known as acheronuk | ||
| === grumble is now known as grumble2 | ||
| === grumble2 is now known as grumble | ||
| karstensrage | rbasak, i thought maybe the packaging used the upstream to figure out how to install things | 22:59 |
| rbasak | karstensrage: ah. Yes, usually it does. You can override that though. | 23:30 |
| karstensrage | ok so if i changed how en existing package works due to changing upstream | 23:42 |
| karstensrage | is that ok | 23:42 |
| karstensrage | ? | 23:42 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!