Re: a slightly updated rpm spec file for Ger Hobbelt crm114 branch
Paolo <[email protected]>
| Newsgroups | gmane.mail.spam.crm114 |
|---|---|
| Message-ID | <20090202161851.GC28290@localhost> |
On Mon, Feb 02, 2009 at 03:07:07PM +0100, Ger Hobbelt wrote: ... > > Really, CVE-like listing turns out to be (also) another marketing tool. > > What about putting in some easter-egg? some dbl-free()? some null-pointer? > > Really? I always understood you'd rather /not/ show up there, unless seems you're lacking an MBA (as I do, btw), sorry ;) > > some weird stuff in the logs and reports to the ML. > > Or ditches the tool and moves on to the next. Bug reports sitting yes, but that's a matter of cost > So? I don't hear an argument for file-based here. crm114 as it is didn't put any effort in naming one, actually - countless people use fs-based tools in countless apps (*awk, *sed, you-name-it), having crm114 into the toolbag too, with its nice feats - albeit still so fs bounded - is already a big service. > using that when you like/want, and the core is usable in a slew of > other domains as well. So it's still a 1-stop shop for those who like > it to be. > Besides, what's the problem with writing a mem+callback-based core > like that? Is it that hard? Nope. Take the current code and the point is, that - unless I've missed something - nobody is arguing against it - again it's a matter of cost, we're just sitting @bottom of a cost pocket, we need some quantum strong enough to leap over the border and drop @bottom of a deeper basin. I.e. someone motivated enough & capable enough to kick the baby beyond the border ;) E.g. @present I'm fine with such fs-limits, I'm on *nix only, I've already got a number of wrappers and work-arounds in place to cover my needs since long, even on an old Piii-450. > Indeed. Though forks tend to cost more in the grand scheme of things > and I'd rather not have that. So be it. the total cost matters, 1+ fork(s) do cost, but agreeing on common way of doing things costs too. Apparently, the balance isn't always in favour of the latter, till/unless some special event/situation occurs. -- paolo ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword