Re: [aur-general] Is it necessary to create a new package just for an dependency header

Hi, Thanks, but that's not the issue. I could create a patch or use sed, if I knew the right way to package this. The main question is wether it is better to include that header (originally not belonging to another program)

For better understanding: On 24/04/15 20:46, Sebastian Lau wrote: that should be: "(originally belonging to another program)"

in the google C++ APIs package (since no other package needs that file) or to create an extra package like mongoose3 with that file only (since that would be the right way - it is an header from another program). Regards, Sebastian