Option to pack default ackrc into script about ack2 HOT 2 CLOSED

I can see wanting to easily carry around your ackrc with you in one package.

Two big problems jump out at me:

• What does the new ack-with-baked-in-ackrc get called? Is it still called ack? How do I know? What kind of surprise am I in for if I'm on a machine that has this rebaked ack on it? Then again, we have that kind of problem if you're on a machine with a weird /etc/ackrc, too.
• At that point ack is self-modifying, and that frightens me. Does baked-in-ack allow rebaking itself?

from ack2.

I think that I would have it write the new ack on standard out. This way, you name it what you want, and if you replace "dough" ack with "baked" ack, you probably know what you're doing.

You bring up an interesting point about baking an already-baked ack. For the being, I would have the bake code check if $App::Ack::is_baked is true, like so:

  if($App::Ack::is_baked) {
    die "Don't!  You'll burn your ack!\n";
  }

I'm ok with "baking" being only a build option, ex. make baked. I see a little benefit in allowing ack --bake, but not enough to justify its inclusion if the community is against it. No matter what, though, ack --debug would have to show that it's consulting an internal rules list rather than /etc/ackrc and friends.

That actually brings up another interesting question: do the baked rules only supplant the global ackrc, or the global + user, or what? I'll have to think about that a bit.

from ack2.