> Steven,
>
> How do you personally handle needing to install software with custom
> command line options in something like Redhat?
I don't know about RedHat. I do know about Debian.
In Debian there are a couple of options. My perferred option would probably
be:
Use "apt-get source <package>". Edit debian/control to change the name
of the package. Set a "Provides:" line to the original name of the package.
(Any package depending on the original package will be happy with this one.)
Set a "Conflicts:" line to the name of the original package. (You can not
have both packages installed at once.)
Then you can make configure-time changes in debian/rules. (Search for
"configure". It will either be in a "configure" section, or in the "build"
section.)
You may want to create a patch file so you can apply this change in the
future, when a new version is released.
Then it is a matter of creating the new package. I usually just use
"fakeroot ./debian/rules binary" but then I don't usually worry about
creating source packages.
Note: This is based upon my believing that you wanted to use custom
command-line options to configure the product. If you're talking about
run-time options, then for services, they would typically be handled with
a configuration file in /etc/default which is referenced by the init
script located in /etc/init.d.
Cheers,
Steven Black
_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug
No comments:
Post a Comment