You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Hudson <gh...@MIT.EDU> on 2003/11/01 05:50:54 UTC
Re: use svn:externals for build/generator/ezt.py?
On Thu, 2003-10-30 at 19:00, Greg Stein wrote:
> Yesterday, I moved ezt.py into a Subversion repository in its own "mini
> project". If we wanted to, we could start pulling ezt into the SVN working
> copy via svn:externals.
I'd be +1 on throwing out svn:externals before we reach 1.0, so I'm -0
on using it ourselves.
(Yeah, I know we have some people using it, mostly for internal
references, and they'd be sad. But I'm pretty convinced that keeping
them happy isn't worth the ick.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: use svn:externals for build/generator/ezt.py?
Posted by kf...@collab.net.
Julian Foad <ju...@btopenworld.com> writes:
> > +1 from me, too. It doesn't seem to be a sound basis for
> > development after version 1. We will be stuck with pressure to
> > continue supporting and enhancing it in a backward-compatible manner.
>
> Oh, what would I know? I've just read Karl's message saying that it
> is an OK basis for development. I should have kept quiet.
:-) Heh, well, I think your position is quite reasonable. Just to
clarify, I'm really saying it's an OK user interface for further
development. What happens under the hood will get revamped quite a
bit -- just the property values themselves will stay the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: use svn:externals for build/generator/ezt.py?
Posted by Julian Foad <ju...@btopenworld.com>.
I (Julian Foad) wrote:
> Greg Hudson wrote:
>
>> On Thu, 2003-10-30 at 19:00, Greg Stein wrote:
>>
>>> Yesterday, I moved ezt.py into a Subversion repository in its own "mini
>>> project". If we wanted to, we could start pulling ezt into the SVN
>>> working
>>> copy via svn:externals.
>>
>> I'd be +1 on throwing out svn:externals before we reach 1.0, so I'm -0
>> on using it ourselves.
>
> +1 from me, too. It doesn't seem to be a sound basis for development
> after version 1. We will be stuck with pressure to continue supporting
> and enhancing it in a backward-compatible manner.
Oh, what would I know? I've just read Karl's message saying that it is an OK basis for development. I should have kept quiet.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: use svn:externals for build/generator/ezt.py?
Posted by Julian Foad <ju...@btopenworld.com>.
Greg Hudson wrote:
> On Thu, 2003-10-30 at 19:00, Greg Stein wrote:
>
>>Yesterday, I moved ezt.py into a Subversion repository in its own "mini
>>project". If we wanted to, we could start pulling ezt into the SVN working
>>copy via svn:externals.
>
> I'd be +1 on throwing out svn:externals before we reach 1.0, so I'm -0
> on using it ourselves.
+1 from me, too. It doesn't seem to be a sound basis for development after version 1. We will be stuck with pressure to continue supporting and enhancing it in a backward-compatible manner.
> (Yeah, I know we have some people using it, mostly for internal
> references, and they'd be sad. But I'm pretty convinced that keeping
> them happy isn't worth the ick.)
Yes.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: use svn:externals for build/generator/ezt.py?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Nov 1, 2003, at 12:50 AM, Greg Hudson wrote:
> On Thu, 2003-10-30 at 19:00, Greg Stein wrote:
>> Yesterday, I moved ezt.py into a Subversion repository in its own
>> "mini
>> project". If we wanted to, we could start pulling ezt into the SVN
>> working
>> copy via svn:externals.
>
> I'd be +1 on throwing out svn:externals before we reach 1.0, so I'm -0
> on using it ourselves.
>
> (Yeah, I know we have some people using it, mostly for internal
> references, and they'd be sad. But I'm pretty convinced that keeping
> them happy isn't worth the ick.)
+1.
It's a hack, it didn't work out as well as we'd hoped and it has so
many unforseen problems that it just isn't worth keeping around.
Better to axe it now and do it right in the future.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: use svn:externals for build/generator/ezt.py?
Posted by kf...@collab.net.
Greg Hudson <gh...@MIT.EDU> writes:
> I'd be +1 on throwing out svn:externals before we reach 1.0, so I'm -0
> on using it ourselves.
>
> (Yeah, I know we have some people using it, mostly for internal
> references, and they'd be sad. But I'm pretty convinced that keeping
> them happy isn't worth the ick.)
I understand the sentiment. This is a borderline case, but I think we
should keep them. It's not costing us that much these days, and the
feature is helping a lot of people (generally in larger organizations,
I think, based on list mails, irc, and private communications).
Also, there is a long-term plan for handling svn:externals cleanly,
and the property format doesn't change in that plan. So the values
people set today will one day behave very cleanly in the working copy,
instead of only, uh, mildly cleanly as they do now. (That long term
plan is alluded to near the end of issue #959, but I thought we had
captured it more completely somewhere. Does anyone remember where?
It's the idea of including foreign items into a .svn/entries file as
first class objects -- in other words, mixing data from different
repositories cleanly in a single working copy.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org