Nope, I understand what you want, I just don't know if it's a good idea. So my thought experiment was to wonder if we'd do the same for the other configuration files.
As in, where is the line drawn? On 4 Feb 2010, at 19:05, till wrote: > Hey Noah, > > anything I can do to clear this up, or better explain what I (or well, > "we" want)? > > Here's a rundown: > > ./configure --couchdb-user=root \ > --couchdb-stdout-file=/my/log/file/for/stdout \ > --couchdb-stderr-file=/my/log/file/for/stderr \ > --couchdb-respawn-timeout=10 \ > --couchdb-pidfile=/home/till/noah.pid > > ... essentially, this would populate /etc/defaults/couchdb. > > Till > > On Thu, Feb 4, 2010 at 7:30 PM, Noah Slater <[email protected]> wrote: >> I'm unsure. >> >> Would he accept a patch for ./configure that set default values in local.ini >> too? >> >> On 4 Feb 2010, at 16:51, Paul Davis wrote: >> >>> Thoughts Noah? I don't immediately see anything wrong with this, but I >>> don't know if other packager people have different expectations. >>> >>> On Thu, Feb 4, 2010 at 11:06 AM, till <[email protected]> wrote: >>>> Hey guys, >>>> >>>> when I install couchdb e.g. on ubuntu, it creates a couple settings in >>>> /etc/default/couchdb. >>>> >>>> I was wondering what you guys think about adding ./configure switches >>>> for each one of them (COUCHDB_USER, COUCHDB_STDOUT_FILE, >>>> COUCHDB_STDERR_FILE, COUCHDB_RESPAWN_TIMEOUT)? =) >>>> >>>> It sure would make my life even easier. :D >>>> >>>> Thoughs? >>>> Till >>>> >> >>
