Karl Fischer wrote:
2009/8/25 Evan Prodromou <[email protected]>:
StatusNet: the Open Source microblogging software
How will this effect Laconica instances 0.8 to upgrade to StatusNet 0.8.1,
won't the name change break stuff ?
Our goal is /not/ to make the upgrade break stuff.
There are only a few places in the code that the name "Laconica" matters:
* /etc/laconica is the default dir for laconica config files. It's
been changed to /etc/statusnet, but the software will still check
/etc/laconica.
* The User-Agent for HTTP client calls is usually "Laconica" or some
standards-violating mangled version thereof. It will be
"StatusNet/0.8.1", which may cause problems for server software
that's filtering on User-Agent.
* There are a few events that use the name "Laconica". Those will
now use "StatusNet", but we'll also fire the events with the old
names, in case some code uses it.
* There are a couple of defines that use LACONICA; these will remain
defined.
* The laconica.po files in the translations have been renamed to
statusnet.po, and the code uses those. If you made a custom
laconica.po, it will not work; you'll need to rename it and
re-compile it.
* The only CSS selector with "laconica" in it is
"site_laconica_license"; it wasn't used in any of the default
themes, and it's an ID, so it's been changed with no backwards
compatibility. Doubt anybody used this externally, except people
wanting to hide the license link. Those people deserve to lose.
As far as I can tell, you shouldn't see any breakage for themes and
plugins. But please test the testing version now, and let us know. Top
priority to fix any bugs caused by the rename.
-Evan
--
Evan Prodromou
CEO, Control Yourself, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
