[06:28] <dholbach> good morning
=== lan3y is now known as Laney
=== mchro- is now known as mchro
=== broder_ is now known as broder
=== \b is now known as benonsoftware
=== s1aden is now known as sladen
=== davroman1ak is now known as davromaniak
[12:59] <sidi> Rethorical question: there's no way to know, looking at the contents of a .deb package, which files will be given the executable flag once the package is installed? I have to actually install the package and manually check the files' permissions, correct?
[13:00] <rbasak> sidi: know for certain, or just get an idea? Most files shipped in debs already have their executable bits set. But it is in theory possible for a package to set or remove the bits in a package postinst.
[13:00] <rbasak> That would be an odd thing to do in most cases though.
[13:01] <rbasak> "set" as in "decided", not "set to 1".
[13:01] <mitya57> sidi, use dpkg -c foo.deb
[13:01] <mitya57> It will show the files permissions
[13:01] <sidi> (damn, pressing Ctrl+W to erase a word in Xchat does not work as expected)
[13:02] <mitya57> <mitya57> sidi, use dpkg -c foo.deb
[13:02] <mitya57> <mitya57> It will show the files permissions
[13:02] <sidi> rbasak, sorry i missed your last message
[13:02] <rbasak> sidi: know for certain, or just get an idea? Most files shipped in debs already have their executable bits set. But it is in theory possible for a package to set or remove the bits in a package postinst.
[13:02] <rbasak> "set" as in "decided", not "set to 1".
[13:02] <sidi> thanks
[13:02] <rbasak> That would be an odd thing to do in most cases though.
[13:02] <rbasak> (change things int he package postinst)
[13:03] <sidi> mitya57, rbasak so i can just download all the debs and grep on top of dpkg -c, that'd work for me I believe
[13:04] <sidi> rbasak, i'll gladly ignore postinst changes if that's not the usual method for setting permissions. i can fix my list of executables later on for individual packages
[13:04] <rbasak> Yep, that should give you a pretty good view. There are probably a few edge cases where files on an installed system don't end up with the same permissions as shipped in the package, but that is probably fairly rare.
[13:06] <sidi> I mainly want to avoid manually doing it for tens of thousands of packages :-) that should be fine
=== shadeslayer_ is now known as shadeslayer