General
-
Support file roles (like executable files)
If I'm distributing a tool through pearhub, I will want a way to have the script file(s) installed in a standard path and made executable. I'm new to PEAR packages in general, but my understanding is that the conventional way to do this would be to set the role of the file in my package.xml file.
Is there currently a way to make this happen through pearhub? If not, it'd be nice to have.
The less intrusive the better - I want my packages to be usable right out of the tarball, so that messy @php_bin@ stuff isn't attractive to… more
21 votes -
Make it possible to include release notes
Release notes for each package would make it easier for the end user to know whether an upgrade would be necessary. Could be implemented via some sort of standard changelog in the repos, which pearhub looks for on each package creation.
8 votes -
Information on when a new repository will be available for use
Information on when a new repository will be available for use.
8 votes -
7 votes
-
Allow OpenID from Google
Right now, despite the fact that Pearhub uses OpenID, it's incompatible with Google's OpenID, and so I'm unable to actually use it (unless I create a new OpenID account somewhere else, but that kind'a eliminates the point of OpenID, doesn't it?).
It would be even better if, like this site, there is a one-click box for popular OpenID providers like Google and Yahoo, but that would be just an added bonus.
6 votes -
Include externals and submodules in package
When pulling code from sources like GitHub, PearHub should (1) pull the code, (2) run `git submodule update --init --recursive` to include all external code, then (3) package it up all PEAR-like. For Subversion repos, it would be a matter of including the svn:externals code.
5 votes -
Add support for mercurial repositories
Some people prefer mercurial as their SCM. This is a suggestion to add support for this.
3 votes -
Extend the project build status
If the build status is 'failed', there is not telling what went wrong and it seems impossible to rebuild the release. A more verbose build status would help.
3 votes -
Trim package names
Doctrine_Template_Positionable (on page 6 at time of writing) overflows container. The version number spills in to the background.
Trivial but makes the page untidy :p
1 vote -
Add a configurable prefix for automatic release detection
so that a prefix of 'myproject-' would lead to a detection of myproject-vX.Y.Z
1 vote -
Add support for CVS
Some people prefer CVS as their SCM. This is a suggestion to add support for this.
0 votes
