Use `xmake publish` to publish the project libraries as package to repositories

[waruqi]

Currently, these are just early ideas and some design drafts.

While using remote repository packages is now quite convenient, distributing and integrating libraries into your own project can still be somewhat complex. (See: https://xmake.io/guide/package-management/distribute-private-libraries.html)

We can provide xmake publish plugin command to publish own project libraries to remote/local repositories. like maven publish, ./gradle uploadArchives, ...

We can publish our project's libraries to private remote repositories, local repositories, and the official xmake repository.

Custom publication configuration

includes("@builtin/publication")

publication("publication_name")
    set_version("1.0")
    add_targets("foo", "bar")
    set_repository("https://github.com/xmake-io/xmake-repo")
    set_authorization("...")

We can custom publish logic code.

includes("@builtin/publication")

publication("publication_name")
    set_version("1.0")
    add_targets("foo", "bar")
    on_publish(function ()
         -- ...
    end)

Publish to the given private remote repositories

-- using the default publication configuration to publish
xmake publish

-- using the given custom publication configuration to publish in project xmake.lua
xmake publish --publication=[name]

-- publish to the given version and repository
xmake publish [-v 1.0] [--repo=name or url]

-- publish the given targets
xmake publish --targets=foo,bar

-- force to re-publish (override existing package)
xmake publish --force

Publish to the official xmake-repo repository.

We can also automatically create pull requests and submit them to the official xmake-repo repository.

xmake publish --publication=official

We will include some predefined publication configurations to quickly publish to the official xmake-repo repository, as well as other package repositories such as vcpkg, conan, etc.

xmake publish --publication=vcpkg
xmake publish --publication=conan
xmake publish --publication= ...

Publish to the local package repositores

xmake publish --local
xmake publish --local -repo=[name or url] 

Integrate the published packages

If the repository has already been added globally, we do not need to use add_repositories to configure the package repository separately.

add_requires("xxx")

The difference from xmake install

This is different from and does not conflict with xmake install. xmake install is only used to install to the system environment, making it convenient for third-party projects to use. However, for internal integration within an xmake project, this method is not recommended. Using packages for maintenance is a more user-friendly approach and avoids polluting the system environment.

[Stehsaer]

有一些疑惑，举个例子：

xmake publish --publication=official

他的具体行为是什么？毕竟xrepo这种是需要通过PR提交的，这个预想中是自动clone然后自动commit？

我认为如下方案会更好：

1. 指定"library scheme"和本地的仓库地址，例如：

xmake publish --scheme=xrepo --path=/home/username/dev/xmake-repo --branch=publish-my-package-branch --target=xxx --name=my-package ...

2. 执行后，xmake自动在指定的path中创建名为publish-my-package-branch的分支，然后将生成的文件（xmake.lua）放到packages/m/my-package。这时候我们手动进到这个目录里面，就可以看到Changes。
3. 然后，我们就可以根据不同的需求去做下一步，例如直接commit到自己的fork然后PR，或者在本地做一下测试，不通过就回滚修改等等

这种方案能给予更大的灵活性，直接push可能会面临鉴权、PR、项目规范、CI/CD之类的问题，让xmake只把生成的文件写入本地clone好的repo能够适应不同的仓库要求，且不需要面对上面提到的问题。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I have some doubts, for example:

xmake publish --publication=official

What was his specific behavior? After all, xrepo needs to be submitted through PR. Is this expected to be automatically cloned and then automatically committed?

I think the following solution would be better:

1. Specify "library scheme" and local warehouse address, for example:

xmake publish --scheme=xrepo --path=/home/username/dev/xmake-repo --branch=publish-my-package-branch --target=xxx --name=my-package ...

2. After execution, xmake automatically creates a branch named public-my-package-branch in the specified path, and then puts the generated file (xmake.lua) into packages/m/my-package. At this time, when we manually enter this directory, we can see Changes.
3. Then, we can take the next step according to different needs, such as directly committing to our own fork and then PR, or doing a test locally, rolling back the modification if it does not pass, etc.

This solution can give greater flexibility. Direct push may face problems such as authentication, PR, project specifications, CI/CD, etc. Let xmake only write the generated files into the local cloned repo to adapt to different warehouse requirements without facing the problems mentioned above.

[waruqi]

有一些疑惑，举个例子：

xmake publish --publication=official
他的具体行为是什么？毕竟xrepo这种是需要通过PR提交的，这个预想中是自动clone然后自动commit？

这只是举个例子而已，可以自动创建个 pr ，当然官方仓库的发布 优先级不高，主要用于本地仓库，内网私仓的发布

我认为如下方案会更好：

1. 指定"library scheme"和本地的仓库地址，例如：

xmake publish --scheme=xrepo --path=/home/username/dev/xmake-repo --branch=publish-my-package-branch --target=xxx --name=my-package ...

指定仓库路径，名字，target ，我上面的例子有啊，一样的，只是参数名的区别

xmake publish [-v 1.0] [--repo=name or url]
xmake publish --targets=foo,bar

但每次指定这么长很麻烦，如果项目中配置了 publication 配置，里面包含了 版本，targets, 仓库地址等各种配置，
那默认情况下，只需一个 xmake publish

如果 xmake.lua 配置了多个仓库配置，只需要 xmake publish --publication=xxx 不更简单么？ 但这并不是说没了灵活性，同时再指定 repo url ，branch， version 什么的，肯定还是可以灵活改写的。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I have some doubts, for example:

xmake publish --publication=official
What was his specific behavior? After all, xrepo needs to be submitted through PR. Is this expected to be automatically cloned and then automatically committed?

This is just an example. You can automatically create a PR. Of course, the release of the official warehouse has a low priority. It is mainly used for the release of local warehouses and intranet private warehouses.

I think the following solution would be better:

1. Specify "library scheme" and local warehouse address, for example:

xmake publish --scheme=xrepo --path=/home/username/dev/xmake-repo --branch=publish-my-package-branch --target=xxx --name=my-package ...

Specify the warehouse path, name, and target. My example above is the same. The only difference is the parameter name.

xmake publish [-v 1.0] [--repo=name or url]
xmake publish --targets=foo,bar

But it is troublesome to specify such a long length every time. If the publication configuration is configured in the project, it contains various configurations such as version, targets, warehouse address, etc.
Then by default, just one xmake publish

If xmake.lua is configured with multiple warehouse configurations, wouldn't it be simpler to just run xmake publish --publication=xxx? But this does not mean that there is no flexibility. At the same time, if you specify the repo url, branch, version, etc., you can definitely rewrite it flexibly.