使用Composer添加包(通过SVN)

时间:2012-12-30 19:31:03

标签: php svn composer-php packagist

我为我的个人PHP库创建了一个SVN存储库,并在根级别添加了一个composer.json文件:

{
        "name": "myPersonalLibrary/lib",
        "type": "library",
        "description": "Light MVC framework for PHP 5.4",
        "keywords": ["database","mvc"],
        "homepage": "http://mysite.com",
        "license": "MIT",
        "require": {
                "php": ">=5.3.0",
                "mustache/mustache": "dev-master"
        },
        "autoload": {
                "psr-0": {
                        "bbn": "src"
                }
        }
}

然后我使用以下composer.json创建了一个项目:

{
    "require": {
        "monolog/monolog": "1.0.*",
        "zerkalica/php-code-sniffer": "dev-master",
        "mustache/mustache": "dev-master",
        "myPersonalLibrary/lib": "*"
    },
    "repositories": [
            {
                    "type": "svn",
                    "url": "https://mysite.com/svn/myPersonalLibrary",
                    "branches-path": false,
                    "tags-path": false,
                    "trunk-path": "src"
            }
    ]
}

当我尝试更新我的项目时,我得到:No valid composer.json was found in any branch or tag of https...

我认为问题来自我的文件结构,但我找不到任何关于此的文档:

/my_repo
  /src
    /lib
      /api
      /db
      /file
      /html
      ....
      /mvc.php
      /obj.php
  /composer.json

我尝试在packagist.org上发布我的网址并获得No valid/supported repository was found at the given URL

2 个答案:

答案 0 :(得分:12)

如果您使用官方推荐的存储库布局和"项目根" (其中包含三个子目录:/trunk/branches/tags),这应该适合您:

对于您的PHP库,在trunk中的项目根目录中创建composer.json(并提交它)。例如:

{
    "name": "myProject/myLibrary",
    "description": "My Personal Library",
    "license": "proprietary",
    "require": {
        "php": ">=5.3"
    },
    "autoload": {
        "classmap": ["src/"]
    }
}

假设您的图书馆资源库位于http://svn.example.com/path/to/myLibrary。然后布局是:

/path/to/myLibrary
  /trunk
    /composer.json
    /src
      ...
  /branches
  /tags

然后在您想要使用库的项目中,使用以下内容创建composer.json:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "http://svn.example.com/path/to/myLibrary"
        }
    ],
    "require": {
        "nette/nette": "~2.2",
        "myProject/myLibrary": "@dev"
    }
}

如果您的主干中只有@dev,那么关键是使用composer.json作为库的必需版本。从trunk创建标记后,您可以开始使用版本号。例如,如果您svn copy ^/trunk ^/tags/1.0.0,则可以使用"myProject/myLibrary": "~1.0"作为版本号。

答案 1 :(得分:3)

尝试获取更多有关 composer update -v 的信息,以获取可以使用的可能版本字符串列表。

我举例说明了获取信息的正确名称是这个配置:

{
    "name": "sample/test",
    "type": "library",
    "version": "0.0.0",
    "time" : "2013-04-16",
    "description": "Testing ...",
    "repositories": [
        {
            "type": "svn",
            "url": "http://framework.zend.com/svn/framework/standard"
        }
    ],
    "require": {
        "php": ">=5.3.3",
        "zendframework/zendframework1" : "dev-trunk"
    }
}

使用 -v 作为参数调用作曲家,如果找到,您将获得分支,标签和主干的列表。我不知道是否允许 false 作为标签和分支的路径......

$ composer update -v
Loading composer repositories with package information
Reading composer.json of zendframework/zendframework1 (release-0.1.1)
Skipped tag 0.1.1, no composer file was found
Reading composer.json of zendframework/zendframework1 (release-0.1.2)
Skipped tag 0.1.2, no composer file was found
Reading composer.json of zendframework/zendframework1 (release-0.1.3)
Skipped tag 0.1.3, no composer file was found
....
Reading composer.json of zendframework/zendframework1 (release-1.9.6)
Importing tag 1.9.6 (1.9.6.0)
Reading composer.json of zendframework/zendframework1 (release-1.9.7)
Importing tag 1.9.7 (1.9.7.0)
Reading composer.json of zendframework/zendframework1 (release-1.9.8)
Importing tag 1.9.8 (1.9.8.0)
Reading composer.json of zendframework/zendframework1 (trunk)
Importing branch trunk (dev-trunk)
Reading composer.json of zendframework/zendframework1 (bughuntday)
Skipped branch bughuntday, no composer file was found
Reading composer.json of zendframework/zendframework1 (development-2.0)
Skipped branch development-2.0, no composer file was found
Reading composer.json of zendframework/zendframework1 (pdo_ibm_ids_support)
Skipped branch pdo_ibm_ids_support, no composer file was found
Reading composer.json of zendframework/zendframework1 (release-1.0)
Importing branch release-1.0 (dev-release-1.0)
Reading composer.json of zendframework/zendframework1 (release-1.10)
Importing branch release-1.10 (dev-release-1.10)
....
Reading composer.json of zendframework/zendframework1 (release-1.8)
Importing branch release-1.8 (dev-release-1.8)
Reading composer.json of zendframework/zendframework1 (release-1.9)
Importing branch release-1.9 (dev-release-1.9)
Reading composer.json of zendframework/zendframework1 (rob_allen)
Skipped branch rob_allen, no composer file was found
Reading composer.json of zendframework/zendframework1 (user)
Skipped branch user, no composer file was found
Updating dependencies (including require-dev)

您可以安全地忽略此行的所有例外情况,它会告诉您必须设置为所请求的版本:

Importing branch trunk (dev-trunk)