You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Régis Priqueler <li...@aizenko.com> on 2003/07/23 16:13:11 UTC
Export question
Hello
Export didn't seems to take care of the externals.
I was searching a way to publish my websites from the repository. I
got a subdir with link (externals) to modules needed by the site.
I was thinking that Export would give me a complete tree with
externals included.
Did I missed something?
Or is there an other way around?
Thanks
--
Régis Priqueler
Portfolio: http://R208.com
Aïzenko: http://aizenko.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Export question
Posted by John Peacock <jp...@rowman.com>.
Régis Priqueler wrote:
>
> It's what i was thinking to do finally but as i'm new to Apache i
> don't know haow to achive this.
>
Here's the instructions from the dev list:
http://www.contactor.se/~dast/svn/archive-2003-07/1403.shtml
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re[2]: Export question
Posted by Régis Priqueler <li...@aizenko.com>.
Hello John,
Thursday, July 24, 2003, 4:04:17 PM, you wrote:
JP> Régis Priqueler wrote:
>> TH> In that way you could put your work in progress into a branch and merge back
>> TH> to head to publish. Svn:externals defiantly does work on update.
>>
>> Yes but all the .svn directories will be present on the published web
>> site.
JP> So what? Use your web server's configuration to forbid traversal of those
JP> directories if you are really worried about it. It is very common to do this
JP> same thing with CVS, with the same caveats.
It's what i was thinking to do finally but as i'm new to Apache i
don't know haow to achive this.
Best regards
--
Régis Priqueler
Portfolio: http://R208.com
Aïzenko: http://aizenko.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Export question
Posted by John Peacock <jp...@rowman.com>.
Régis Priqueler wrote:
> TH> In that way you could put your work in progress into a branch and merge back
> TH> to head to publish. Svn:externals defiantly does work on update.
>
> Yes but all the .svn directories will be present on the published web
> site.
So what? Use your web server's configuration to forbid traversal of those
directories if you are really worried about it. It is very common to do this
same thing with CVS, with the same caveats.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re[4]: Export question
Posted by Paul Lussier <pl...@lanminds.com>.
In a message dated: Thu, 24 Jul 2003 10:03:48 +0200
=?ISO-8859-1?B?UulnaXMgUHJpcXVlbGVy?= said:
>Hello Tim,
>
>Thursday, July 24, 2003, 12:39:47 AM, you wrote:
>
>TH> Could you not just put a WC on the webserver and load the svn client on it
>TH> and do a scheduled "update".
>
>TH> In that way you could put your work in progress into a branch and merge back
>TH> to head to publish. Svn:externals defiantly does work on update.
>
>Yes but all the .svn directories will be present on the published web site.
Errr, can't you configure the web server to ignore .svn directories?
I could've sworn I just saw a post about that very subject here[1]
recently. I'm almost positive Apache allows for this type of thing.
[1] 'here' being loosely defined as "this list" which means it oculd
have been on the dev@ list from which users@ was recently split :)
--
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
It may look like I'm just sitting here doing nothing,
but I'm really actively waiting for all my problems to go away.
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re[4]: Export question
Posted by Régis Priqueler <li...@aizenko.com>.
Hello Tim,
Thursday, July 24, 2003, 12:39:47 AM, you wrote:
TH> Could you not just put a WC on the webserver and load the svn client on it
TH> and do a scheduled "update".
TH> In that way you could put your work in progress into a branch and merge back
TH> to head to publish. Svn:externals defiantly does work on update.
Yes but all the .svn directories will be present on the published web
site.
Best regards
--
Régis Priqueler
Portfolio: http://R208.com
Aïzenko: http://aizenko.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re[2]: Export question
Posted by Tim Hawkins <ti...@timhawkins.co.uk>.
Could you not just put a WC on the webserver and load the svn client on it
and do a scheduled "update".
In that way you could put your work in progress into a branch and merge back
to head to publish. Svn:externals defiantly does work on update.
-----Original Message-----
From: Régis Priqueler [mailto:lists@aizenko.com]
Sent: 23 July 2003 17:44
To: Garrett Rooney
Cc: users@subversion.tigris.org
Subject: Re[2]: Export question
Hello Garrett,
Wednesday, July 23, 2003, 6:34:28 PM, you wrote:
GR> If you like, you can file a bug about this problem, and someone will
GR> probably get to it at some point.
I'm coming from the discussion on the other forum.
So you've got the responses to your questions there ;-)
I was thinking of an other way to implement it. But this
functionality is relatively simple (once you had
understood the way props are working) and would be complete for me
with an option in export to use them.
Best regards
--
Régis Priqueler
Portfolio: http://R208.com
Aïzenko: http://aizenko.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re[2]: Export question
Posted by Régis Priqueler <li...@aizenko.com>.
Hello Garrett,
Wednesday, July 23, 2003, 6:34:28 PM, you wrote:
GR> If you like, you can file a bug about this problem, and someone will
GR> probably get to it at some point.
I'm coming from the discussion on the other forum.
So you've got the responses to your questions there ;-)
I was thinking of an other way to implement it. But this
functionality is relatively simple (once you had
understood the way props are working) and would be complete for me
with an option in export to use them.
Best regards
--
Régis Priqueler
Portfolio: http://R208.com
Aïzenko: http://aizenko.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Export question
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Régis Priqueler wrote:
> Hello
>
> Export didn't seems to take care of the externals.
>
> I was searching a way to publish my websites from the repository. I
> got a subdir with link (externals) to modules needed by the site.
>
> I was thinking that Export would give me a complete tree with
> externals included.
>
> Did I missed something?
> Or is there an other way around?
No, you didn't miss anything, most likely it's yet another example of a
Subversion command that doesn't work well with svn:externals. Someone
who is sufficiently motivated will have to add support for svn:externals
to svn_client_export. That person will most likely not be me, as I
think the entire svn:externals feature is a waste of time and effort on
our part, but hey, whatever floats your boat.
If you like, you can file a bug about this problem, and someone will
probably get to it at some point.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org