Mailbox Requesting Authentication
Hello developers-reference, Please Notice there is shipment to you. Check Below the shipping documents from last order. Folangsi Co.,Ltd Add: No.13, Bangyan Road, Bangjiangdong, Shiji Town,Panyu District,Guangzhou,China
Bug#1017446: debian-policy: stress that preinst script that install by using base64 decode on self an elf binary is not a good stuff
roucaries> No the problem is not probing the cpu/cpuinfo... Well, if the CPU info could be probed from shell, I'd argue that's better than unpacking a binary. roucaries> The problem is the base64 encoded binary. Why is this bad. I agree that it is esthetically displeasing, but *in this instance*, why is it harmful? roucaries> I ma solving this by pre-depends on a binary package and roucaries> run the binary from the preinstalled package. I would have been less caustic in my reply than Adam, but made the same point. Having multiple packages is more complex, especially in a situation where the binary in question is only used by the preinst. It may be there are concerns I'm not seeing that make the current arrangement worse than taht. But let's actually articulate them.
Bug#1017446: debian-policy: stress that preinst script that install by using base64 decode on self an elf binary is not a good stuff
On Wed, Aug 17, 2022 at 08:09:09AM +, roucaries bastien wrote: > Le mar. 16 août 2022 à 13:22, Sam Hartman a écrit : > > > "Bastien" == Bastien Roucariès writes: > > Bastien> I will like to stress that this kind of stuff is bad: > > Bastien> > > https://salsa.debian.org/debian/isa-support/-/blob/master/debian/altivec-support.preinst.in#L10 > > > > How would you do better in that instance? > > I think everyone knows it's bad, but I'm guessing that the maintainer > > didn't have a better approach for detecting whether the referenced > > instructions worked on the installed system. > The problem is the base64 encoded binary. > > I ma solving this by pre-depends on a binary package and run the > binary from the preinstalled package. So you think having 10 binary packages instead of 5, all of them shipping just a single file, and a Pre-Depends between them, is preferable to unpacking a temporary file? The choice was obvious to me. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase. ⠈⠳⣄
Bug#1017446: debian-policy: stress that preinst script that install by using base64 decode on self an elf binary is not a good stuff
Le mar. 16 août 2022 à 13:22, Sam Hartman a écrit : > > > "Bastien" == Bastien Roucariès writes: > Bastien> I will like to stress that this kind of stuff is bad: > Bastien> > https://salsa.debian.org/debian/isa-support/-/blob/master/debian/altivec- > Bastien> support.preinst.in#L10 > > How would you do better in that instance? > I think everyone knows it's bad, but I'm guessing that the maintainer > didn't have a better approach for detecting whether the referenced > instructions worked on the installed system. > > I'm assuming that if feature tests in /proc/cpuinfo were sufficient they > would have been used. No the problem is not probing the cpu/cpuinfo... The problem is the base64 encoded binary. I ma solving this by pre-depends on a binary package and run the binary from the preinstalled package. > > --Sam
