I confess that we have our extensions in /usr/local/wiki-extensions,
which is an svn checkout of our local repository. For us, it makes
two things easier:
1) I've been known to stupidly delete the extensions directory when
upgrading MW
2) different wikis share the single directory.
But when
Aryeh Gregor wrote:
> On Thu, Aug 13, 2009 at 3:24 PM, Ilmari Karonen wrote:
>> You don't need symlinks for that, a simple "svn switch" works just fine.
>
> Could you explain in more detail? I don't get how that would work.
From memory (don't feel like doing a new checkout over this crappy wlan
2009/8/14 Brion Vibber :
>> On my production wiki I have phase3/ checked out in
>> /var/www/w, and some extensions individually checked out in
>> subdirectories of /var/www/w/extensions. When I do svn up in
>> /var/www/w, that doesn't update the other repositories in extensions/;
>> I have to do
On Thu, Aug 13, 2009 at 9:12 PM, Brion Vibber wrote:
> svn up works just fine for this too in my experience. Perhaps your
> 'extensions' dir isn't SVN-managed for some reason, or something?
It has a .svn directory in it . . . of course, I use git for
development anyway. It's worked so far, so I d
On 8/13/09 4:51 PM, Aryeh Gregor wrote:
> On Thu, Aug 13, 2009 at 7:40 PM, Brion Vibber wrote:
>> On 8/13/09 3:32 PM, Aryeh Gregor wrote:
>>> Then what do I do if I want to commit to both phase3/ and extensions/
>>> at once?
>>
>> svn commit
>
> This works in SVN if you have two checkouts nested w
On Thu, Aug 13, 2009 at 7:40 PM, Brion Vibber wrote:
> On 8/13/09 3:32 PM, Aryeh Gregor wrote:
>> Then what do I do if I want to commit to both phase3/ and extensions/
>> at once?
>
> svn commit
This works in SVN if you have two checkouts nested within each other?
Don't commands like commit and di
On 8/13/09 3:32 PM, Aryeh Gregor wrote:
> On Thu, Aug 13, 2009 at 2:25 PM, Brion Vibber wrote:
>> Why? Just put your extensions in the extensions folder where they belong.
>
> Then what do I do if I want to commit to both phase3/ and extensions/
> at once?
svn commit
> Or even just check both o
On Thu, Aug 13, 2009 at 2:25 PM, Brion Vibber wrote:
> Why? Just put your extensions in the extensions folder where they belong.
Then what do I do if I want to commit to both phase3/ and extensions/
at once? Or even just check both of them out at once? Am I supposed
to maintain several repositor
On Thu, Aug 13, 2009 at 4:17 PM, Bryan Tong
Minh wrote:
> On Thu, Aug 13, 2009 at 3:43 AM, Aryeh
> Gregor wrote:
>> On Wed, Aug 12, 2009 at 5:03 PM, Brion Vibber wrote:
>>> Your setup is incorrect: the extensions folder *always* goes inside the
>>> MediaWiki root dir. Always.
>>
>> I don't do this
On Thu, Aug 13, 2009 at 3:43 AM, Aryeh
Gregor wrote:
> On Wed, Aug 12, 2009 at 5:03 PM, Brion Vibber wrote:
>> Your setup is incorrect: the extensions folder *always* goes inside the
>> MediaWiki root dir. Always.
>
> I don't do this on my development wiki. I use a checkout of trunk, so
> extensio
Aryeh Gregor wrote:
>
> It's a problem that may or may not have a good solution. If nobody
> can come up with a good solution, then I guess there's no good
> solution. But symlinking stuff works just fine for almost every
> extension out there right now, and is convenient if you have a single
>
On 8/13/09 10:55 AM, Aryeh Gregor wrote:
> On Thu, Aug 13, 2009 at 1:06 PM, Brion Vibber wrote:
>> In any case they need to be able to find and reach that setup info,
>> which is what a stable directory tree provides.
>
> Yes, that's the puzzle. I guess extensions could special-case the
> trunk c
That's the reason why I always symlink extensions/ to my common
extensions folder.
/path/to/common/extensions/
/path/to/mywiki/*
/path/to/mywiki/extensions -symlink-> /path/to/common/extensions/
/path/to/anotherwiki/*
/path/to/anotherwiki/extensions -symlink-> /path/to/common/extensions/
It works
On Thu, Aug 13, 2009 at 5:16 AM, Dmitriy Sintsov wrote:
> MW_INSTALL_PATH is great, but it can cause the inclusion from the
> another MediaWiki installation on the same server (once I've had such
> error on v1.14 farm and v1.15 "alone for testing purposes") .
> What about going down to path looking
On 8/12/09 6:43 PM, Aryeh Gregor wrote:
> On Wed, Aug 12, 2009 at 5:03 PM, Brion Vibber wrote:
>> Your setup is incorrect: the extensions folder *always* goes inside the
>> MediaWiki root dir. Always.
>
> I don't do this on my development wiki. I use a checkout of trunk, so
> extensions/ is insid
* Leons Petrazickis [Thu, 13 Aug 2009
10:35:51 -0400]:
> On Thu, Aug 13, 2009 at 05:16, Dmitriy Sintsov
> wrote:
> > I wish MediaWiki had farm-friendly LocalSettings.php (loading
> different
> > set of $wg* variables according to host name), which would not
require
> > symlinks (not available in
On Thu, Aug 13, 2009 at 05:16, Dmitriy Sintsov wrote:
> I wish MediaWiki had farm-friendly LocalSettings.php (loading different
> set of $wg* variables according to host name), which would not require
> symlinks (not available in Windows).
Actually, symlinks are available in Windows as the NTFS ju
On 13/08/2009, at 10:16 AM, Dmitriy Sintsov wrote:
> I wish MediaWiki had farm-friendly LocalSettings.php (loading
> different
> set of $wg* variables according to host name), which would not require
> symlinks (not available in Windows). I do use Linux for hosting, but
> sometimes I have to deb
* Daniel Friesen [Wed, 12 Aug 2009 15:33:50
-0700]:
> Take a good second look at the chunk of code you posted.
>
> $IP = getenv( 'MW_INSTALL_PATH' );
> if ( $IP === false ) {
> $IP = dirname(__FILE__).'/../..';
> }
>
> This is precisely the reason the MW_INSTALL_PATH environment variable
>
On Wed, Aug 12, 2009 at 5:03 PM, Brion Vibber wrote:
> Your setup is incorrect: the extensions folder *always* goes inside the
> MediaWiki root dir. Always.
I don't do this on my development wiki. I use a checkout of trunk, so
extensions/ is inside phase3/../. Are there any significant problems
dan nessett wrote:
> --- On Wed, 8/12/09, Brion Vibber wrote:
>
>
>> Your setup is incorrect: the extensions folder *always*
>> goes inside the
>> MediaWiki root dir. Always.
>>
>>
>
> Sorry, my inexperience with Subversion led me in the wrong direction. I
> didn't realize I could check
On Wed, Aug 12, 2009 at 6:04 PM, dan nessett wrote:
> --- On Wed, 8/12/09, Brion Vibber wrote:
>
>> Your setup is incorrect: the extensions folder *always*
>> goes inside the
>> MediaWiki root dir. Always.
>>
>
> Sorry, my inexperience with Subversion led me in the wrong direction. I
> didn't rea
--- On Wed, 8/12/09, Brion Vibber wrote:
> Your setup is incorrect: the extensions folder *always*
> goes inside the
> MediaWiki root dir. Always.
>
Sorry, my inexperience with Subversion led me in the wrong direction. I didn't
realize I could check out phase3 then point Subversion to the ext
On 8/12/09 1:39 PM, dan nessett wrote:
> This works on a deployed version of MW, since the extensions
> directory is embedded in /phase3. But, in a development version,
> where /extensions is a separate subdirectory
Your setup is incorrect: the extensions folder *always* goes inside the
MediaWiki
Chad wrote:
> DumpHTML will not be moved back to maintenance in the repo, it was
> already removed from maintenance and made into an extension. Issues
> with it as an extension should be fixed, but it should not be encouraged
> to go back into core.
What I meant was I can move the code in DumpH
On Wed, Aug 12, 2009 at 4:39 PM, dan nessett wrote:
> So. I checked out a copy of phase3 and extensions to start working on
> investigating the feasibility of a comprehensive parser regression test.
> After getting the working copy downloaded, I do what I usually do - blow away
> the extensions
So. I checked out a copy of phase3 and extensions to start working on
investigating the feasibility of a comprehensive parser regression test. After
getting the working copy downloaded, I do what I usually do - blow away the
extensions directory stub that comes with phase3 and soft link the down
27 matches
Mail list logo
