Bug: bea/e30

ID :	e30e2b6b-acc9-4b93-88c6-b63b6e30b593
Short name :	bea/e30
Status :	open
Severity :	minor
Assigned :
Reporter :	W. Trevor King <wking@drexel.edu>
Creator :	W. Trevor King <wking@drexel.edu>
Created :	Mon, 01 Feb 2010 14:28:13 +0000
Summary :	Where should the vcs-name and encoding configuration options live?

Comment:

--------- Comment ---------
ID: 2cd562f5-fcb9-4cc5-bf8c-ad5c9d960761
Short name: bea/e30/2cd
From: W. Trevor King <wking@drexel.edu>
Date: Mon, 01 Feb 2010 14:34:10 +0000

Before Bugs Everywhere Directory v1.4 we kept
  "encoding"
  "vcs_name"
and other bugdir-wide configuration options in ./be/settings

Now we don't store them anymore, but we should keep some.  For
example, the encoding setting is useful when running `be html` in a
cron job.  The settings are repository wide, so they should _still_ go
in ./be/settings (since there may, eventually, be several bugdirs in a
repo), but who's job is it to read that file?

The user interface takes care of encoding, but the storage object 
would be checking for a bug repository and reading the settings file.
How/when does it notify the UI?

Comment:

--------- Comment ---------
ID: 68ec74b9-d2c7-421f-ac70-602b43bbd263
Short name: bea/e30/68e
From: W. Trevor King <wking@drexel.edu>
Date: Mon, 01 Feb 2010 15:35:57 +0000

On the other hand, since encoding decisions seem to be locale-driven,
so you can just setup the appropriate locale environmental variables
in your cron job:
  export LANG=en_US.utf8
and that should do it...