| Updating repository > live copy |
[Jan. 20th, 2008|06:30 am] |
There is one thing that isn't clear in the documentation and seems to be something we're "supposed to know" regarding updating from the trunk (and I obviously don't "know" it).
Okay, so, you run 'svn up' to update the repository. That's all fine and good. But what do you run after that to transfer the updated repository to the working copy? THAT has never been laid out anywhere, and the LJ documentation still refers to cvsreport, which I understand is obsolete and no longer used.
Do you have to re-run these two commands:
vcv/bin/vcv --conf=multicvs.conf --checkout
vcv/bin/vcv --conf=multicvs.conf --init
or is there an svn-specific command you run?
Also, it would seem you have to know the version number(s) in order to roll back a revision, am I right, or is there an easier way to do it via svn?
Thanks for any help. |
|
|
| Source code for /misc/fdata.bml |
[Jan. 20th, 2008|05:28 pm] |
|
Dear LJ developers,
The source code for /misc/fdata.bml doesn't appear in the public Subversion repository. It looks like it's been missing from there for historical reasons. Could you please add /misc/fdata.bml to the repository?
When I asked for this in October 2006, a moderator of ![[info]](http://p-stat.livejournal.com/img/community.gif) lj_dev rejected my post with the following message:
"The source is not really useful. It's simply `load up to 1000 users and show them'."
In fact, the source is useful for two audiences: those who run LiveJournal-based websites and those who are designing and debugging crawlers that fetch the friends data. The (yet unpublished?) documentation on XML Userdata vaguely states that "fdata.bml may be considered a best effort type of system. It is not designed to be effective on users/communities with excessively large groups of friends". If I could find out how and when the fdata.bml output differs from the real state of affairs, I could optimize my crawler not to fetch the same data again through other means just to see if it might be more accurate that what fdata.bml provides.
As a bonus, if you publish the source, you might get some patches that fix bugs or make fdata.bml more useful. LiveJournal is still supposed to be GPL, isn't it? |
|
|
