Submitting ebuild for phpWebSite CMS application. A la phpBB and others, this ebuild downloads the tarball and unpacks it into the apache DocumentRoot.
Created attachment 10129 [details] net-www/phpwebsite/phpwebsite-0.9.0.ebuild
Created attachment 10130 [details] net-www/phpwebsite/files/digest-phpwebsite-0.9.0
Should this go into net-www/phpwebsite or dev-php/phpwebsite? We have: dev-php/phpsysinfo dev-php/phpgroupware dev-db/phpmyadmin dev-db/phppgadmin net-www/phpBB app-office/phprojekt
I had assume net-www since that was where phpBB was. I leave it up to you though.
I guess I could see it being in dev-php, since I develop modules for it. I wouldn't put it in dev-db since it isn't a tool like phpmyadmin. It is a CMS like phpgroupware. Just an FYI that phpWebSite 0.9.1 will be out and about within the week and I'll post the ebuild for that when it is.
Created attachment 10645 [details] phpwebsite-0.9.1.ebuild
Created attachment 10646 [details] files/digest-phpwebsite-0.9.1
phpWebSite 0.9.1 was released today as promised. New ebuild and digest are attached. Marking old ones obsolete.
Don: 1. Write up an initial Changelog please (look up skel.Changelog in portage). 2. A comment about the ebuild. What about installing as "phpwebsite-version" with a symlink to "phpwebsite". That way upgrading is easier later on, and you can get rid of the die in pkg_setup. I'm really busy with final exams at the moment, and you doing these will make life easier so your package gets in sooner.
Answers: 1. (re: ChangeLog) No problem I'll start on that. 2. (re: different directories) The issue with that is the intended way to upgrade is to install the new code over the old code and then go through the web interface. So I actually WOULD want to install into the same directory.
Created attachment 10680 [details] ChangeLog Added the changelog. Basically I just copied the release notes from the actual release, which didn't have dates for each of the changes.
"The issue with that is the intended way to upgrade is to install the new code over the old code and then go through the web interface. So I actually WOULD want to install into the same directory." In that case, why is there the check for a pre-installed warning that dies if you already have it installed?
Probably because I'm a careless idiot who was just copying the phpBB ebuild and not thinking at the time of phpWebSite's upgrade situation.
Should I update the ebuild to not do that check, or can you do that?
we can remove it for you. i'm currently working on a new release of PHP/mod_php and somebody else is going to be picking up these ebuilds shortly. Just looking at the changelog you posted, does your application have a changelog that contains the same data? The changelog we keep is for changes in the ebuilds, not the application.
Oh yes that ChangeLog was for the application itself. I suppose the Changelog should be blanked out except for the header then since this would be the first ebuild for this application.
I was planning to update this. As I said the code for the new should just be copied over the old, however the files in the conf directory probably shouldn't be overwritten, and perhaps notice given. I'll look into how best to put this into effect, but if you have any thoughts I'd love to hear them.
Going to attach what I have for now.
Created attachment 14472 [details] net-www/phpwebsite/phpwebsite-0.9.2_p1.ebuild Adding package ebuild and marking old ebuild obsolete.
Created attachment 14473 [details] net-www/phpwebsite/ChangeLog Adding new ChangeLog for initial package add and marking old one obsolete
Created attachment 14474 [details] net-www/phpwebsite/files/digest-phpwebsite-0.9.2_p1 Adding new digest and marking old one obsolete.
So there they all are. Still need to preserve existing conf directory.
Actually phpwebsite doesn't come with a config file, it is generated on install, so we are good here.
submitted courtesy of our very own rizzo the rat! enjoy
