ZF Pear Channel Proposal
|
View:
New views
14 Messages
—
Rating Filter:
Alert me
|
 |
ZF Pear Channel Proposal
by GavinZend
::
Rate this Message:
I have a green light from the Zend team for proposing this popular idea
to the Server Management Team: Why? - Friendly way to install *all* of the ZF, using well-known processes. - Easy to update. - Easy way to share an installation of ZF across multiple ZF apps. - Easy way to provide access to "developer" release, although SVN is preferred. Where? - Community Development Server. Todo - Create the pear channel. - Create/update pear "components" (ZF preview release, and a developer release). - Add a wiki page explaining how to add and use the new pear channel. All credits go to the many community members who first proposed this idea. Cheers, Gavin |
|
|
Re: [fw-general] ZF Pear Channel Proposal
by Stefan Koopmanschap
::
Rate this Message:
A very good idea indeed, this will probably be a boost in adoption for certain userfriendly-addicted people ;)
On 10/4/06, Gavin Vess <gavin@...> wrote: I have a green light from the Zend team for proposing this popular idea -- Stefan Koopmanschap http://www.stefankoopmanschap.nl/ http://www.leftontheweb.com/ |
|
|
Re: [fw-general] ZF Pear Channel Proposal
by Andries Seutens
::
Rate this Message:
Gavin this is great news!
This will hopefully boost the amount of people testing developer components as well. I'm primarely looking at the Zend_Locale team here, which barely received feedback/test results on their hard work. We had the same issues with the manual. It was a serious hassle if people wanted to help out with the translation of the manual (svn, cygwin, compiling, docbook, ...). By making the switch to wiki, the manual will be much more accessible. Hopefully the same thing will happen with the pear channel that also offers to download the developer releases. Best regards, Andries Seutens Belgium http://andries.systray.be Gavin Vess schreef: > I have a green light from the Zend team for proposing this popular > idea to the Server Management Team: > > Why? > - Friendly way to install *all* of the ZF, using well-known processes. > - Easy to update. > - Easy way to share an installation of ZF across multiple ZF apps. > - Easy way to provide access to "developer" release, although SVN is > preferred. > > Where? > - Community Development Server. > > Todo > - Create the pear channel. > - Create/update pear "components" (ZF preview release, and a developer > release). > - Add a wiki page explaining how to add and use the new pear channel. > > All credits go to the many community members who first proposed this > idea. > > Cheers, > Gavin |
|
|
Re: ZF Pear Channel Proposal
by cyberlot
::
Rate this Message:
Will hopefully be able to work on this some tonight after I get a good
days sleep ;) I would assume we are going to put each "block" into its own package, Like Zend, Zend_Mail, Zend_Pdf and so on right? Gavin Vess wrote: > I have a green light from the Zend team for proposing this popular idea > to the Server Management Team: > > Why? > - Friendly way to install *all* of the ZF, using well-known processes. > - Easy to update. > - Easy way to share an installation of ZF across multiple ZF apps. > - Easy way to provide access to "developer" release, although SVN is > preferred. > > Where? > - Community Development Server. > > Todo > - Create the pear channel. > - Create/update pear "components" (ZF preview release, and a developer > release). > - Add a wiki page explaining how to add and use the new pear channel. > > All credits go to the many community members who first proposed this idea. > > Cheers, > Gavin > |
|
|
Re: ZF Pear Channel Proposal
by GavinZend
::
Rate this Message:
Oh, I meant to say that there would be only two pear packages, one for
ZF preview release, and one for ZF developer release. In this way, we can deliver the entire ZF as one package. For numerous reasons, we absolutely want to avoid breaking ZF up into pieces with different revision/version numbers. Cheers, Gavin Richard Thomas wrote: > Will hopefully be able to work on this some tonight after I get a good > days sleep ;) > > I would assume we are going to put each "block" into its own package, > Like Zend, Zend_Mail, Zend_Pdf and so on right? > > Gavin Vess wrote: >> I have a green light from the Zend team for proposing this popular >> idea to the Server Management Team: >> >> Why? >> - Friendly way to install *all* of the ZF, using well-known processes. >> - Easy to update. >> - Easy way to share an installation of ZF across multiple ZF apps. >> - Easy way to provide access to "developer" release, although SVN is >> preferred. >> >> Where? >> - Community Development Server. >> >> Todo >> - Create the pear channel. >> - Create/update pear "components" (ZF preview release, and a >> developer release). >> - Add a wiki page explaining how to add and use the new pear channel. >> >> All credits go to the many community members who first proposed this >> idea. >> >> Cheers, >> Gavin >> > > |
|
|
RE: [fw-general] ZF Pear Channel Proposal
by Charles-32
::
Rate this Message:
This is an excellent idea. Maybe we could have two channels, like Symphony.
One for the latest build, and one for the latest "milestone" build. http://www.symfony-project.com/content/download.html -- Charles |
|
|
Re: [fw-general] ZF Pear Channel Proposal
by thomasW
::
Rate this Message:
You can do this by defining the release state you want to have...
Within pear you can say "default" or "alpha". $ pear config-set preferred_state alpha Greetings Thomas ----- Original Message ----- From: "Charles" <lists06@...> To: <fw-server@...>; "'Zend Framework General'" <fw-general@...> Sent: Wednesday, October 04, 2006 8:02 PM Subject: RE: [fw-general] ZF Pear Channel Proposal > This is an excellent idea. Maybe we could have two channels, like > Symphony. > One for the latest build, and one for the latest "milestone" build. > > http://www.symfony-project.com/content/download.html > > -- Charles > > |
|
|
Re: ZF Pear Channel Proposal
by Ole Bendik Kvisberg
::
Rate this Message:
Gavin Vess wrote:
> Oh, I meant to say that there would be only two pear packages, one for > ZF preview release, and one for ZF developer release. In this way, we > can deliver the entire ZF as one package. For numerous reasons, we > absolutely want to avoid breaking ZF up into pieces with different > revision/version numbers. > I have hacked together a script tonight, which at least could be something for Richard to work from. Feel free to do whatever you like, including changing the name :), Richard. I would normally have written this as a shell script, but I tried to create a PHP script instead. The script uses three PEAR modules and the pear command: require 'Console/Getargs.php'; require 'VersionControl/SVN.php'; (not in stable release) require 'PEAR/PackageFileManager.php'; First it exports 'library'ยน anonymously from the ZF SVN server, then it generates an package.xml file and finally wraps it all up in a .tgz using the command 'pear package' from within the build directory. It only supports exporting the latest 'svn release' right now, but making the script able to handle stable as well as 'nightly build' should not be a big issue. The creation of the server/channel is left untouched. If any one is interested, the script is downloadable from: http://olekvi.users.linpro.no/zf/pearify/pearify.php.txt It should be in SVN - where? Some examples (sorry for broken lines): olekvi@ws:~/workspace/PEARify Zend Framework$ ./pearify.php -h Usage: pearify.php [-hd --build-dir --pear-cmd --skip-svn-export --svn-cmd --svn-url] --build-dir=<value> Override default builddir (/tmp/pearify) -d --debug Enable debugging -h --help Show this help --pear-cmd=<value> Override default pear executable (/usr/bin/pear) --skip-svn-export Skip SVN export - for testing --svn-cmd=<value> Override default svn executable (/usr/bin/svn) --svn-url=<value> Override default SVN URL for Zend Framework (http://framework.zend.com/svn/framework/trunk/library) olekvi@ws:~/workspace/PEARify Zend Framework$ ./pearify.php -d Starting SVN Export (this may take some time..) Writing package.xml file in /tmp/pearify Creating tgz file for the package in /tmp/pearify Running command: /usr/bin/pear package You should now have a package.xml file and a .tgz file in/tmp/pearify Please clean up manually for now... olekvi@ws:~/workspace/PEARify Zend Framework$ ls -l /tmp/pearify/ total 344 -rw-r--r-- 1 olekvi olekvi 26505 2006-10-04 22:01 package.xml drwxr-xr-x 19 olekvi olekvi 4096 2006-10-04 22:01 Zend -rw-r--r-- 1 olekvi olekvi 302592 2006-10-04 22:01 Zend-0.1.6a.tgz -rwxr-xr-x 1 olekvi olekvi 11255 2006-06-08 23:42 Zend.php Note: The script will not clean up anything, yet. 1: LICENSE.txt and README.txt is *not* in 'library' and hence left out of the package right now. -- Ole Bendik Kvisberg Linpro AS |
|
|
Re: ZF Pear Channel Proposal
by GavinZend
::
Rate this Message:
Since some may want to install both the most recent stable release, and
the latest developer release, perhaps we want to support this using two differently named pear "components"? How many would actually want to download both? Is it better to make things "easier" by marking both the pear "components" (preview release and developer release) as "stable" in pear, or should the unstable/svn/nightly snapshot be marked as alpha, and thus require the pear command below, before it could be downloaded and installed using pear? If we leave the developer component requiring the pear command below, it will make it harder for ordinary PHP users to accidentally grab the wrong version. In the relatively near future, the majority of downloaders will want the "stable" release, not a nightly snapshot. Cheers, Gavin Thomas Weidner wrote: > You can do this by defining the release state you want to have... > Within pear you can say "default" or "alpha". > > $ pear config-set preferred_state alpha > > Greetings > Thomas > > ----- Original Message ----- From: "Charles" <lists06@...> > To: <fw-server@...>; "'Zend Framework General'" > <fw-general@...> > Sent: Wednesday, October 04, 2006 8:02 PM > Subject: RE: [fw-general] ZF Pear Channel Proposal > > >> This is an excellent idea. Maybe we could have two channels, like >> Symphony. >> One for the latest build, and one for the latest "milestone" build. >> >> http://www.symfony-project.com/content/download.html >> >> -- Charles >> >> > > |
|
|
Re: Re: ZF Pear Channel Proposal
by cyberlot
::
Rate this Message:
I agree, we should have the stable as the default, and force using more
detailed pear commands to download other versions. We could then have a 1.6n = nightly snapshot Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Gavin Vess wrote: > Since some may want to install both the most recent stable release, and > the latest developer release, perhaps we want to support this using two > differently named pear "components"? How many would actually want to > download both? > > Is it better to make things "easier" by marking both the pear > "components" (preview release and developer release) as "stable" in > pear, or should the unstable/svn/nightly snapshot be marked as alpha, > and thus require the pear command below, before it could be downloaded > and installed using pear? > > If we leave the developer component requiring the pear command below, it > will make it harder for ordinary PHP users to accidentally grab the > wrong version. In the relatively near future, the majority of > downloaders will want the "stable" release, not a nightly snapshot. > > Cheers, > Gavin > > Thomas Weidner wrote: >> You can do this by defining the release state you want to have... >> Within pear you can say "default" or "alpha". >> >> $ pear config-set preferred_state alpha >> >> Greetings >> Thomas >> >> ----- Original Message ----- From: "Charles" <lists06@...> >> To: <fw-server@...>; "'Zend Framework General'" >> <fw-general@...> >> Sent: Wednesday, October 04, 2006 8:02 PM >> Subject: RE: [fw-general] ZF Pear Channel Proposal >> >> >>> This is an excellent idea. Maybe we could have two channels, like >>> Symphony. >>> One for the latest build, and one for the latest "milestone" build. >>> >>> http://www.symfony-project.com/content/download.html >>> >>> -- Charles >>> >>> >> >> > |
|
|
Re: ZF Pear Channel Proposal
by thomasW
::
Rate this Message:
> Since some may want to install both the most recent stable release, and
> the latest developer release, perhaps we want to support this using two > differently named pear "components"? How many would actually want to > download both? I thought that the developer release would include "library" and "incubator" directories so it holds the complete actual SVN... The stable release will only hold the library directory. So anybody who wants to use the developer release has only to extend the included directories. > Is it better to make things "easier" by marking both the pear "components" > (preview release and developer release) as "stable" in pear, or should the > unstable/svn/nightly snapshot be marked as alpha, and thus require the > pear command below, before it could be downloaded and installed using > pear? This could leave to problem with people not sure which version they should install... Better let the stable version be the standard and the developer release alpha. My 2 cents ;-) Greetings Thomas |
|
|
|
|
|
|
|
|
Re: Re: Server Setup
by cyberlot
::
Rate this Message:
I fixed the issue with the php.ini being replaced so at this point I
think we just need a few admins to get in, get there hands dirty and report back to us what they feel needs to be changed. Maybe some more docs on how to do various specific tasks, I don't know how detailed we need to be, the people using this service should all be developers so I don't think we need a "how to for dummies" level of detail but still. Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Gavin wrote: > Hi guys, > > What is left on the todo list, before we can formally launch the > community server? > > Cheers, > Gavin > > Richard Thomas wrote: >> Sorry for the late response on this one, >> >> Currently the only problem file looks to be php.ini as thats where any >> pecl/custom extensions and settings would be dropped, its trival to >> have it back that up if it already exists. >> >> As to php4, The only way to "replace" php4 is to install php5 by rpm >> so ensim can handle it, there where some major problems with this so I >> avoided it, also this way allows for easier self compiles on a per >> virtual host basis. >> >> Richard Thomas - CEO >> Cyberlot Technologies Group Inc. >> 507.398.4124 - Voice >> >> >> Ole Bendik Kvisberg wrote: >>> Regarding copying; We could provide a 'per install file' in which users >>> could write down filenames, with regex support, for files the don't want >>> overwrited? (placing a regex which match 'everything' should be >>> possible.) One filename (or regex) per line. >>> >>> Should be pretty easy writing a shell, or maybe better a php or perl >>> script, to do this? >>> foreach my $file (@files) { >>> copy($file) unless (grep { $file =~ /$_/ } @notCopyFileRegExps); >>> } >>> >>> Another approach could be to keep an 'database' or mtime for all copied >>> files, and if file.mtime > database.mtime at copy.time we should either >>> skip all such files, or 'mv file file.$(date --iso-8601)' before >>> copying. >>> >>> >>> Regarding PHP4: Do we need it? (My guess is Ensim uses it?) >>> >>> >>> Ole Bendik >>> >>> >>> Richard Thomas wrote: >>>> Our php5.sh setup script for ensim needs some tender love >>>> >>>> /etc/appliance/customization/php5 >>>> >>>> This script copies php5 over on site setup and site change, The >>>> problem is it does so without haste, in my test case it replaced my >>>> edited php.ini file so I lost access to all my installed pear modules. >>>> >>>> We should prob come up with some sort of upgrade policy, I was >>>> thinking maybe a file each user can change that would "disable" >>>> updates of there files so we don't overwrite then. >>>> >>>> The problem though is say there is an rpm upgrade of php4, That >>>> upgrade is going to "overwrite" some of the file changes and we will >>>> need to "reinstall" php5. >>>> >>>> The current script just blindly copies everything over which replaces >>>> php.ini and would even overwrite someones custom compile of php. >>>> >>>> >>>> >>>> Richard Thomas - CEO >>>> Cyberlot Technologies Group Inc. >>>> 507.398.4124 - Voice >>>> >>>> >>>> Richard Thomas wrote: >>>>> http://pear.zfdev.com/AdMiN.php >>>>> Master Login: zfdev >>>>> Master Pass: temptemp >>>>> >>>>> >>>>> Richard Thomas wrote: >>>>>> I played around with pear.zfdev.com today >>>>>> >>>>>> I added pear.chiaraquartet.net and pear.crtx.org to the available >>>>>> channels, >>>>>> >>>>>> Installed Chira_PEAR_Server and all the required/suggest libraries >>>>>> but it had some problems setting up the DB, recompiling php to >>>>>> include mysqli as it choked on the MDB2 for some weird reason >>>>>> >>>>>> db: pear >>>>>> login: pear >>>>>> password: hv9V:Tm7t5yTQxh5 >>>>>> >>>>>> Richard Thomas - CEO >>>>>> Cyberlot Technologies Group Inc. >>>>>> 507.398.4124 - Voice >>>>>> >>>>>> >>>>>> Ole Bendik Kvisberg wrote: >>>>>>> Richard Thomas wrote: >>>>>>>> Ole has had a chance to browse around a bit, and im starting to >>>>>>>> get a >>>>>>>> little bit of energy back, What do we need to do to really kick >>>>>>>> this off? >>>>>>> We might need some more documentation? >>>>>>> Your answers yesterday about SSH as an example. >>>>>>> >>>>>>> I will be away from 'now' until Monday (for a family wedding), but >>>>>>> after >>>>>>> that I could try to write such documentation. >>>>>>> >>>>>>> >>>>>>> I'm also working on getting pear.zfdev.com up and running one or >>>>>>> more >>>>>>> PEAR-channels. One for 'whole stable package' and one for >>>>>>> 'different >>>>>>> nightly pages' sounds good to me. >>>>>>> >>>>>>> >>>>>>> The Sandbox is working great after Richard told me how it is >>>>>>> supposed to >>>>>>> work (hey; no need for chroot anymore! :-) >>>>>>> >>> >>> >> >> >> > > |
| Free Forum Powered by Nabble | Forum Help |