Re: [pyrus] generate-pear2

On Thu, Jul 8, 2010 at 12:29 AM, till <till@php.net> wrote: > Hey again! =) > > I find a lot of what is created by "generate-pear2" there very confusing. > > For starters - we don't need the trunk, branches, tags dir. A lot of > people use a dvcs such as git. > > Then, there's these files and directories: > API-0.1.0 > RELEASE-0.1.0 > package_compatible.xml > packagexmlsetup.php > stub.php > README > extrasetup.php > customcommand > customroles > customtasks > > ... while it's cool that pyrus can do a lot. It's not very helpful for > people getting into PEAR. I've recently showed this to two people who > have never done a PEAR package before and they didn't feel like > exploring all of that if they didn't have to. For a first timer, it's > time consuming though to figure out what is needed. > > Particularly, I don't understand what API* and RELEASE* are for when I > have package.xml. And what I have to do with package_compatible.xml, > packagexmlsetup.php and extrasetup.php. I'm also thinking that the > stub.php file shouldn't be generated at all and should be instead > created when I do generate-phar. > > All in all, it looks like this is indeed the whole deal of what's > possible with pyrus, but for the sake of avoiding a learning wall, I > think it should be trimmed heavily to not make people deal with all > this if they don't have to. It probably wouldn't hurt to have > documentation on the bits and pieces when people tackled package.xml > and are ready to get deeper into it. > > I also looked up generate-pear2 in the manual, it didn't really > explain much or any of it. > > Last but not least - src/PEAR2/PackageName/Main.php? Maybe I missed > parts of the discussion, but why is that created instead of > src/PEAR2/PackageName.php? > > Till > I also found a bug: <filelist> <install name="php/PEAR2/Foo/Bar/Main.php" as="PEAR2/Foo/Bar/Main.php"/> </filelist> ... should be "src". :-) Till