All geek questions in one place

Zend Framework and svn: external

I am using svn: externals to transfer Zend Framework files to my project. Here is what my svn: externals looks like:

-r 22731 http://framework.zend.com/svn/framework/standard/trunk/library/Zend/ Zend
-r 22731 http://framework.zend.com/svn/framework/extras/trunk/library/ZendX/ ZendX

I linked it to revision 22731, which is a revision of this repository path: http://framework.zend.com/svn/framework/standard/tags/release-1.10.7

I thought this was the preferred way to use external ones, but when I look at the class Zend_Version, I notice what it says const VERSION = '1.11.0dev';. Should I do svn: externals like this instead?

http://framework.zend.com/svn/framework/standard/tags/release-1.10.7/library/Zend/ Zend
http://framework.zend.com/svn/framework/standard/tags/release-1.10.7/extras/library/ZendX/ ZendX
+3
source share
4 answers

Based on the feedback, a hybrid of the two options seems to be the best option:

-r 22731 http://framework.zend.com/svn/framework/standard/tags/release-1.10.7/library/Zend/ Zend
-r 22731 http://framework.zend.com/svn/framework/standard/tags/release-1.10.7/extras/library/ZendX/ ZendX

Here are my thoughts:

  • trunk
  • , , .
+2

, , .

, , ' , . , .

UPDATE: MWOP. , . - - , , , , .

+3

1.10.7 - 22830, 22731. .

I prefer to check my external links. Having a release version number is much more convenient than a long version number.
If I use tags, I know that this is a released (stable) version.

+2
source

You definitely MUST use the tag for external external checks. There is no need to search for a specific revision. These are tags made for;)

+1
source

Source: https://habr.com/ru/post/1759372/

More articles:


All Articles