Geek Answers Handbook

What is the best practice for saving libraries from their real projects

For some reason, I recently started to create my own library. It started out as a simple library with some useful classes, but since it is still growing every day, and I have already used it in some projects, it has become impossible to track changes since I did not use SVN.

Now I started using SVN, I wanted to add a library, as well as projects to another SVN repository. One for each project (since the library is also a project).

What is the best way to keep my library separate from the project? Each project has a directory /library/in which all sorts of libraries are stored. So what is my best practice:

  • I could add a directory /library/framework/and set it to ignore in the SVN of the project, and then check the library in that directory (is this possible?)
    • Pro : each project has its own structure, if the infrastructure can change, it will not break any code in the project.
    • Con : If I have 100 projects and they all need a substantial upgrade (safe), I have to upgrade them all manually.
  • I could also check the library somewhere on the server and symbolize the directory /library/framework/after ignoring it in the svn project.
    • Pro : one update fixes all projects in the event of a significant update.
    • Con : As mentioned above: one update will fix / change all projects ...
    • Con: , ( ...)

- ?

+5
2

svn externals . dir , externals .

, IMO - , , //.

+3

.

.htaccess( apache-2 - [1]), -

php_value include_path /absolute/path/to/libraries:/absolute/path/to/my/project:/lib/3rd_party

.., git/svn-checkouts.

[1] http://httpd.apache.org/docs/2.0/howto/htaccess.html

+1

More articles:


All Articles