| Author |
Message |
< Erlyweb mailing list ~ move mysql + psql driver into repository? |
| Guest |
 Posted: Mon Oct 29, 2007 2:50 am |
 |
|
|
Guest
|
Hi,
I would like to move the code for the MySQL and PSQL drivers into the
repository instead of referencing them using svn:externals. This would
ensure that the db driver version is always in sync with the ErlyDB
version that uses it. Does anybody have any objections?
Thanks,
Yariv
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| rsaccon |
| Posted: Mon Oct 29, 2007 4:24 am |
|
|
|
User
Joined: 09 Aug 2006
Posts: 144
|
No objections. The svn:external just caused trouble when I once tried
to use git for my local SVN copy
Roberto
On Oct 28, 11:50 pm, "Yariv Sadan" <yarivsa...@gmail.com> wrote:
> Hi,
>
> I would like to move the code for the MySQL and PSQL drivers into the
> repository instead of referencing them using svn:externals. This would
> ensure that the db driver version is always in sync with the ErlyDB
> version that uses it. Does anybody have any objections?
>
> Thanks,
> Yariv
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Mon Oct 29, 2007 9:07 am |
|
|
|
Guest
|
Take a look at piston (http://piston.rubyforge.org/) , as it was
designed specifically for this purpose.
How it works is you keep the svn:externals and use piston to lock the
svn:external at your chosen external revision.
The lock revisions are svn:props so they are versioned along with
erlyweb, so when you checkout any version of erlyweb, you get the
correct externals for that version.
Another side benefit of piston is that you get a complete checkout
even if one or more externals are temporarily unavailable. This would
matter greatly if you use 3rd party externals.
Only the server needs to 'gem install piston', not the clients, so
from the clients (our) perspective nothing has changed, but now we
automatically get correct and tested versions of externals for any
given version of erlyweb. Clients could install piston and manually
update their externals, and it is nice that it is possible but is not
required to get the benefit of piston.
A 'pistonized' subversion repository would be tranparent and fully
compatible with Git mirroring.
Also, Git as of v1.5.3 added support for sub-modules (externals), so
now I have no reason to use Subversion.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| rsaccon |
| Posted: Mon Oct 29, 2007 9:57 am |
|
|
|
User
Joined: 09 Aug 2006
Posts: 144
|
Robin, thanks for the clarifications, let's googlecode get
pistonized !!!
On Oct 29, 6:06 am, Robin <robi...@gmail.com> wrote:
> Take a look at piston (http://piston.rubyforge.org/) , as it was
> designed specifically for this purpose.
>
> How it works is you keep the svn:externals and use piston to lock the
> svn:external at your chosen external revision.
>
> The lock revisions are svn:props so they are versioned along with
> erlyweb, so when you checkout any version of erlyweb, you get the
> correct externals for that version.
>
> Another side benefit of piston is that you get a complete checkout
> even if one or more externals are temporarily unavailable. This would
> matter greatly if you use 3rd party externals.
>
> Only the server needs to 'gem install piston', not the clients, so
> from the clients (our) perspective nothing has changed, but now we
> automatically get correct and tested versions of externals for any
> given version of erlyweb. Clients could install piston and manually
> update their externals, and it is nice that it is possible but is not
> required to get the benefit of piston.
>
> A 'pistonized' subversion repository would be tranparent and fully
> compatible with Git mirroring.
>
> Also, Git as of v1.5.3 added support for sub-modules (externals), so
> now I have no reason to use Subversion.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Oct 30, 2007 8:25 am |
|
|
|
Guest
|
Piston looks good, but I don't have the ability to install it on the
server  It looks like the only solution in this case is to import
the externals into the repository. The only potential issue is Google
Code's one-license stance (ErlyWeb is MIT, the externals are BSD) but
I don't think we'll be violating the terms of services.
Yariv
On Oct 29, 2007 2:06 AM, Robin <robi123@gmail.com> wrote:
>
> Take a look at piston (http://piston.rubyforge.org/) , as it was
> designed specifically for this purpose.
>
> How it works is you keep the svn:externals and use piston to lock the
> svn:external at your chosen external revision.
>
> The lock revisions are svn:props so they are versioned along with
> erlyweb, so when you checkout any version of erlyweb, you get the
> correct externals for that version.
>
> Another side benefit of piston is that you get a complete checkout
> even if one or more externals are temporarily unavailable. This would
> matter greatly if you use 3rd party externals.
>
> Only the server needs to 'gem install piston', not the clients, so
> from the clients (our) perspective nothing has changed, but now we
> automatically get correct and tested versions of externals for any
> given version of erlyweb. Clients could install piston and manually
> update their externals, and it is nice that it is possible but is not
> required to get the benefit of piston.
>
> A 'pistonized' subversion repository would be tranparent and fully
> compatible with Git mirroring.
>
> Also, Git as of v1.5.3 added support for sub-modules (externals), so
> now I have no reason to use Subversion.
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Oct 30, 2007 12:59 pm |
|
|
|
Guest
|
Piston does not need to be installed on the actual server. You would
install piston on your laptop, configure the externals, then you
commit to the server, and the repository appears as though the
externals are inline as you desire, but they are truly externals and
you can version them as such from your laptop. The subversion server
does not even know that you are using piston to manage your externals.
On Oct 30, 1:25 am, "Yariv Sadan" <yarivsa...@gmail.com> wrote:
> Piston looks good, but I don't have the ability to install it on the
> server It looks like the only solution in this case is to import
> the externals into the repository. The only potential issue is Google
> Code's one-license stance (ErlyWeb is MIT, the externals are BSD) but
> I don't think we'll be violating the terms of services.
>
> Yariv
>
> On Oct 29, 2007 2:06 AM, Robin <robi...@gmail.com> wrote:
>
>
>
> > Take a look at piston (http://piston.rubyforge.org/) , as it was
> > designed specifically for this purpose.
>
> > How it works is you keep the svn:externals and use piston to lock the
> > svn:external at your chosen external revision.
>
> > The lock revisions are svn:props so they are versioned along with
> > erlyweb, so when you checkout any version of erlyweb, you get the
> > correct externals for that version.
>
> > Another side benefit of piston is that you get a complete checkout
> > even if one or more externals are temporarily unavailable. This would
> > matter greatly if you use 3rd party externals.
>
> > Only the server needs to 'gem install piston', not the clients, so
> > from the clients (our) perspective nothing has changed, but now we
> > automatically get correct and tested versions of externals for any
> > given version of erlyweb. Clients could install piston and manually
> > update their externals, and it is nice that it is possible but is not
> > required to get the benefit of piston.
>
> > A 'pistonized' subversion repository would be tranparent and fully
> > compatible with Git mirroring.
>
> > Also, Git as of v1.5.3 added support for sub-modules (externals), so
> > now I have no reason to use Subversion.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Oct 31, 2007 2:02 pm |
|
|
|
Guest
|
+1 Piston
On Oct 30, 2007 8:58 AM, Robin <robi123@gmail.com> wrote:
>
> Piston does not need to be installed on the actual server. You would
> install piston on your laptop, configure the externals, then you
> commit to the server, and the repository appears as though the
> externals are inline as you desire, but they are truly externals and
> you can version them as such from your laptop. The subversion server
> does not even know that you are using piston to manage your externals.
>
> On Oct 30, 1:25 am, "Yariv Sadan" <yarivsa...@gmail.com> wrote:
> > Piston looks good, but I don't have the ability to install it on the
> > server It looks like the only solution in this case is to import
> > the externals into the repository. The only potential issue is Google
> > Code's one-license stance (ErlyWeb is MIT, the externals are BSD) but
> > I don't think we'll be violating the terms of services.
> >
> > Yariv
> >
>
> > On Oct 29, 2007 2:06 AM, Robin <robi...@gmail.com> wrote:
> >
> >
> >
> > > Take a look at piston (http://piston.rubyforge.org/) , as it was
> > > designed specifically for this purpose.
> >
> > > How it works is you keep the svn:externals and use piston to lock the
> > > svn:external at your chosen external revision.
> >
> > > The lock revisions are svn:props so they are versioned along with
> > > erlyweb, so when you checkout any version of erlyweb, you get the
> > > correct externals for that version.
> >
> > > Another side benefit of piston is that you get a complete checkout
> > > even if one or more externals are temporarily unavailable. This would
> > > matter greatly if you use 3rd party externals.
> >
> > > Only the server needs to 'gem install piston', not the clients, so
> > > from the clients (our) perspective nothing has changed, but now we
> > > automatically get correct and tested versions of externals for any
> > > given version of erlyweb. Clients could install piston and manually
> > > update their externals, and it is nice that it is possible but is not
> > > required to get the benefit of piston.
> >
> > > A 'pistonized' subversion repository would be tranparent and fully
> > > compatible with Git mirroring.
> >
> > > Also, Git as of v1.5.3 added support for sub-modules (externals), so
> > > now I have no reason to use Subversion.
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Nov 01, 2007 6:14 am |
|
|
|
Guest
|
I see. The only disadvantage of keeping externals in this case is
that ErlyWeb developers have to work with source code in multiple
Google Code projects, which is sometimes inconvenient. I like being
able to edit all the source files in the same project together when I
make changes. I just want to make sure Google doesn't object to such
uses of Google Code (which would be kinda silly...)
Yariv
On Oct 30, 2007 5:58 AM, Robin <robi123@gmail.com> wrote:
>
> Piston does not need to be installed on the actual server. You would
> install piston on your laptop, configure the externals, then you
> commit to the server, and the repository appears as though the
> externals are inline as you desire, but they are truly externals and
> you can version them as such from your laptop. The subversion server
> does not even know that you are using piston to manage your externals.
>
> On Oct 30, 1:25 am, "Yariv Sadan" <yarivsa...@gmail.com> wrote:
> > Piston looks good, but I don't have the ability to install it on the
> > server It looks like the only solution in this case is to import
> > the externals into the repository. The only potential issue is Google
> > Code's one-license stance (ErlyWeb is MIT, the externals are BSD) but
> > I don't think we'll be violating the terms of services.
> >
> > Yariv
> >
>
> > On Oct 29, 2007 2:06 AM, Robin <robi...@gmail.com> wrote:
> >
> >
> >
> > > Take a look at piston (http://piston.rubyforge.org/) , as it was
> > > designed specifically for this purpose.
> >
> > > How it works is you keep the svn:externals and use piston to lock the
> > > svn:external at your chosen external revision.
> >
> > > The lock revisions are svn:props so they are versioned along with
> > > erlyweb, so when you checkout any version of erlyweb, you get the
> > > correct externals for that version.
> >
> > > Another side benefit of piston is that you get a complete checkout
> > > even if one or more externals are temporarily unavailable. This would
> > > matter greatly if you use 3rd party externals.
> >
> > > Only the server needs to 'gem install piston', not the clients, so
> > > from the clients (our) perspective nothing has changed, but now we
> > > automatically get correct and tested versions of externals for any
> > > given version of erlyweb. Clients could install piston and manually
> > > update their externals, and it is nice that it is possible but is not
> > > required to get the benefit of piston.
> >
> > > A 'pistonized' subversion repository would be tranparent and fully
> > > compatible with Git mirroring.
> >
> > > Also, Git as of v1.5.3 added support for sub-modules (externals), so
> > > now I have no reason to use Subversion.
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
