|Last Modified:||2016-04-27 12:15:10|
|Version Found In:|
anonymous added on 2015-07-25 18:53:27:
Did you plan to have a composer package of you library?
mario added on 2015-08-28 06:02:42: (text/x-fossil-plain)
Composer doesn't understand fossil repositories. Which is mostly why there isn't one. (Didn't get around to implement that myself, lack of API documentation on composers part.) Also this project is somewhat dated now. Not sure it still makes sense for a wide userbase.
anonymous added on 2016-04-26 09:13:20: (text/x-fossil-plain)
Hi, Would you be opposed to others adding upgradephp to packagist? If not, would you mind if such a package uses `upgradephp/upgradephp` as package name? On a side note, with the current settings it is not possible to clone this project, so any git clone/mirror can only update *all* the code at once instead of copying the incremental commits from the fossil repo. greeting, Potherca
mario added on 2016-04-27 12:11:51: (text/x-fossil-wiki)
Yes, sure. If you want to make a composer bundle out of it, go for it. The package name sounds alright.
mario added on 2016-04-27 12:15:10: (text/x-fossil-wiki)
There is a git export feature, btw: [http://fossil.include-once.org/upgradephp/git-fast-export] However, git itself can't use its own format for incremental imports of course. So I might add a SVN export..