'Re: windows installer, too old?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: koffice-devel
Subject: Re: windows installer, too old?
From: Cyrille Berger <cberger () cberger ! net>
Date: 2009-04-16 9:51:26
Message-ID: 200904161151.27569.cberger () cberger ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Thursday 16 April 2009, you wrote:
> On windows I have disabled krita/ dir long ago, so not quite at least for
> now. What I try to say is that we could split our packaging tasks in order
> to keep the quality. Just like packaging tasks are delegated to
> individual maintainers in case of Linux distros.
That you only want to maintain only kexi package is fine.

But having something that compile would be a first start. Having people that 
compile on a regular basis, and find error early make them much more easier to 
fix, even if it's not the person who do the compilation who make the fix. If you 
are unwilling to build krita on windows, even if it's just to report 
compilation errors, makes me wonder why I should build kexi on linux (and 
sometime on freebsd) and report errors ? (and/or fix them when they are easy). 
Being part of KOffice is also that, build other applications and report errors.

-- 
Cyrille Berger

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; \
font-weight:400; font-style:normal;">On Thursday 16 April 2009, you wrote: &gt; \
On windows I have disabled krita/ dir long ago, so not quite at least for &gt; \
now. What I try to say is that we could split our packaging tasks in order &gt; \
to keep the quality. Just like packaging tasks are delegated to &gt; individual \
maintainers in case of Linux distros. That you only want to maintain only kexi \
package is fine. But having something that compile would \
be a first start. Having people that compile on a regular basis, and find error early \
make them much more easier to fix, even if it's not the person who do the compilation \
who make the fix. If you are unwilling to build krita on windows, even if it's just \
to report compilation errors, makes me wonder why I should build kexi on linux (and \
sometime on freebsd) and report errors ? (and/or fix them when they are easy). Being \
part of KOffice is also that, build other applications and report errors. -- \
 Cyrille Berger</body></html>

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread] 