On Sat, 2008-12-13 at 13:35 +0100, Sebastian Haase wrote:
> Hi Franklin,
> this sound very interesting: so there is a Debian specific script !?
> Is there any online place where one could browse through the mentioned files ?
> (readme, ... + the script )
The script simply invoke "upstream" migrati
Hello Pierre,
On Wed, 2008-12-10 at 21:45 +0100, Pierre Coupard wrote:
> As far as documentation is concerned, the Debian package is quite devoid
> of it, as are most Debian packages.
Short answer:
vim -o /usr/share/doc/$packagename/{NEWS,README}.Debian.gz
Long answer:
As you may know, Debia
On Dec 11, 2008, at 7:35 AM, JT Moree wrote:
> If you find that really great support (moinmoin or other wikis) for
> free let me know. I'd love to have someone else maintain my wikis
> for me. ;)
>
I'm not talking about free support (although I admit it would be
nice), I'm talking about som
2008/12/11 Pierre Coupard :
> Wow, way to mess up an analogy. Apple's MacOS is indeed notoriously bad
> at maintaining backward compatibility, because Apple wants to get rid of
> the old cruft. Microsoft however has an operating system that, however
> bad, still runs DOS software in emulation 30 ye
On Thu, Dec 11, 2008 at 2:12 AM, Pierre Coupard wrote:
> Wow, way to mess up an analogy. Apple's MacOS is indeed notoriously bad
> at maintaining backward compatibility, because Apple wants to get rid of
> the old cruft. Microsoft however has an operating system that, however
> bad, still runs DO
On Wed, 2008-12-10 at 15:29 -0800, Greg Noel wrote:
> You have to cater to us by providing clear,
> explicit, _complete_ documentation about how to upgrade, or we'll look
> elsewhere for someone who makes it easier.
If you find that really great support (moinmoin or other wikis) for free
let m
IL PROTECTED]
Gesendet: Donnerstag, 11. Dezember 2008 09:12
An: moin-user@lists.sourceforge.net
Betreff: Re: [Moin-user] Why oh why!
Rick Vanderveer wrote:
> You cannot have a "legacy" switch because the whole point is to purge
> that ugly code to begin with, if you kept it you&#x
Rick Vanderveer wrote:
> You cannot have a "legacy" switch because the whole point is to purge
> that ugly code to begin with, if you kept it you'd only be tripling
> the work for yourself!
I wasn't talking about keeping the old code around, but having parsers
to convert the old code to the new
> > I ended up making a quick awk script to fix the pages for the new
> > syntax
>
> I'm not a developer so I can't help you with the "legacy" switch but
> could you post your awk script.
Please DON'T post it to the list. It will only confuse people.
And I can assure you that a AWK script is unl
Let me give you my take on this.
On Dec 10, 2008, at 2:54 AM, Thomas Waldmann wrote:
> We provide documentation and expect that people read them ... docs/
> CHANGES contains docs about every noteworthy change we do, ...
Aye, there's the rub. Buried in the blizzard of literally a thousand
tha
Hey Peirre,
Well, you have to understand that part of upgrading the code is doing away
with the flawed design decisions that had become a royal headache to work
around. For example, the code that handled spaces in links/URL's was a
nightmare, and was seriously hampering development. At some point
Pierre Coupard wrote:
> Hey, thanks everybody for your replies.
Hi Pierre,
Are you the Pierre Coupard who worked at Lineo? If so, how's it
going??
I was going to answer your upgrade questions, but other
people beat me to it.
I did an upgrade from 1.5.1 to 1.6.3 earlier this year
and it was a f
On Wed, Dec 10, 2008 at 2:45 PM, Pierre Coupard <[EMAIL PROTECTED]> wrote:
> Hey, thanks everybody for your replies. I apologize if the tone of my
> message sounded nasty or ungrateful, I must admit I had a bout of
> despair when I wrote it.
>
> To address the points you have made: I had backed up
Hey, thanks everybody for your replies. I apologize if the tone of my
message sounded nasty or ungrateful, I must admit I had a bout of
despair when I wrote it.
To address the points you have made: I had backed up the data before
trying the upgrade, so I wasn't in any danger of permanently losi
Pierre,
In addition to everything Thomas and Reimer said, I'd like to add that I
personally keep up with the current releases, and try to document the major
changes and upgrade steps which many find useful. It's also linked directly
from the MoinMoinDownload page, so it's easy to find. :-)
http
Hi Pierre,
I am sorry that you had a bad upgrading experience, but please note:
We provide documentation and expect that people read them (especially,
but not limited to, when doing major upgrades).
docs/CHANGES contains docs about every noteworthy change we do,
including some pointers to some o
Pierre Coupard schrieb:
> Hello everybody,
>
> So, I've used MoinMoin for years. I've advocated it at all my
> workplaces, and each time, my boss and other employees ended up finding
> it great and very useful.
>
> So that's what I did at my new work last year. I installed MoinMoin
> 1.5.somethin
Hello everybody,
So, I've used MoinMoin for years. I've advocated it at all my
workplaces, and each time, my boss and other employees ended up finding
it great and very useful.
So that's what I did at my new work last year. I installed MoinMoin
1.5.something from Debian-stable. I whipped up a cou
18 matches
Mail list logo
