2011/11/26 Slobodan Terzić <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 25.11.2011. 23:34, Allan McRae wrote: >>> >> >> That only works for libalpm/pacman (written in C), not for >> makepkg/pacman-key etc (written in bash...) >> >> Allan >> > > Huh, I thought it's all C. That makes things a lot harder. :( > Thanks for the clarification. > > Any suggestions about this? > I belive that no matter how you change the string, it just wouldn't > fit all languages out there. Also, I think that rewriting scripts in C > (or anything else) instead of bash wouldn't be an option either. At > least not a quick one. > > Best regards, > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iF4EAREIAAYFAk7QKRwACgkQJlCTC65LCjlhbAEAg55H8IoJq88GI0BZ9mhR7kK4 > AdfKT4F5UP+4UnHDJmIA/ReYISYY+3yZiOCH9DTrk7ub5mt3vMbbHGWB6udDyCr2 > =MPnE > -----END PGP SIGNATURE----- > >
So? I don't know any programming language but a bit bash scripting. It is hard to understand for me. Should i look into source code and try to understand if source is written in C, C++, Perl, Python etc.? It is not an ideal solution. What about differing variables. I mean, as written in first post, instead of four %s variables putting %d, %f etc.? Is it possible from the developer view?
