Re: package.xml dir and file problems

On Wed, Jun 29, 2011 at 3:10 AM, rod <rod@pu-gh.com> wrote: > Hi, sorry if this has been asked before, but I've been able to find > very little information on it. > > I am trying to create a PEAR package for a library I have written, but > am having trouble with the contents node.  At the moment it doesn't > quite seem possible to do what I want to do, so need to check.  My > source structure is like this (apologies for possible hacky ascii > diagram) > > root > package.xml > -- bin > ---- Binary scripts > -- lib > ---- LibraryName > ------ LibraryFiles, etc... > > With the package.xml in the root I can't create a package that does > not *also* include the lib folder.  So when I install into PEAR it > comes out as... > > $PEAR/lib/LibraryName > > Rather than... > > $PEAR/LibraryName > > A workaround to this I was using is to move the package.xml inside the > lib folder, which then packages the files correctly.  But, then I'm > unable to access the bin folder to include the scripts in there.  I've > tried using PackageFileManager2 to create the package.xml, and also > hand coding it, and changing around all the combinations of nesting > for dir nodes, and baseinstalldir attributes but having absolutely no > luck. > > Can anyone tell me if what I'm trying to do is even possible, or do I > need to change my source layout to be more PEAR friendly? This is actually pretty close to the new PEAR2 coding standards, only we use php or src dirs, and a scripts dir for bin files. If you have those folders in place, you should be able to use pyrus to generate a package.xml file. http://pear.php.net/manual/en/pyrus.commands.make.php Hope that helps. -- Brett Bieber