pbw wrote:

You're missing the point of how vB plugins in 3.5 work versus phpbb. They rarely touch core code so upgrading is not the huge pain in the ass you'll find it to be next time phpbb comes out with a new version.

and it was merely a suggestion, no need to act condescending. I just assumed you might be less close minded, and open to a thought on ways that might make life easier down the road. I wasnt insisting the idea be used at all, just thought it might be listened to. Was trying to help, as i've used both phpbb and vB extensively.
I wasn't being condescending - I was making a point and you have helped prove it.

I have implemented the changes in a wholey transparent and reversible way by creating patches rather than just storming in an editing the code - of course the database changes aren't quite so easy for me but I have all the details for the sql commands and I am sure someone can provide the reverse of all of them.

However, aside from all that, what has occured to me is that the easiest way to to maintain the phpbb would be as an Arch pkg. By creating a tarball snapshot of the forum as it is now and creating a PKGBUILD that applies the patches and installs the new files it would be easy to keep track of the changes. When a new version is released it will be much easier to track the changes in the old code versus the new code and fix the patches accordingly - I find it hard to believe phpbb will change quite that much tho.

Phil

On Saturday 03 September 2005 11:37 am, Philip Dillon-Thiselton wrote:
pbw wrote:
Alright, though it allows for seamless integration with gallery and
mediawiki. *shrug*.

Just a suggestion, since that way you wouldnt have such a big job doing
mods, since alot of the features would already be included. And upgrading
versions in the future will be a huge pain with a hacked up phpbb.
OK - here's a pet project for you.  You go and check which mods we are
adding and then come back and post which of the is included in vbulletin
already as standard.

Thanks :)

On Saturday 03 September 2005 11:12 am, Philip Dillon-Thiselton wrote:
pbw wrote:
If a new improved forum is on the agenda. Why not use vBulletin rather
than hacking up phpbb? imo it's vastly superior. Also, it's simple to
import phpbb userbase and threads.
Simply, no.  It's a big enough job doing the mods, thanks.  Plus it
means a new system, blah, blah, blah.

On Saturday 03 September 2005 10:55 am, Philip Dillon-Thiselton wrote:
Hello,

As the new Forum Techical Adviser (how did i fall for that?) I have set
up a demo site to test out and develop the mods proposed for the Arch
site.  All of the mods are decribed and list on the site so discussions
should take place there.

Most importantly it is impossible to test the site without a user base
and people doing the posting.  This is your chance to have your say
about what you would like from the forum, I have already incorporated
one excellent suggestion.

So, please, come over sign up and get posting and help us create the
future of the Arch Forums,

http://www.jiwe.org/phpbb

Anyone skilled in php is also going to be an asset as somethings could
use some fixing :)

Phil

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch



_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to