Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jul 2000 15:37:31 -0300 (ADT)
From:      The Hermit Hacker <scrappy@hub.org>
To:        Will Andrews <andrews@technologist.com>
Cc:        Satoshi Asami <asami@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/converters/kdesupport2 Makefile ports/games/kdegames2 Makefile ports/misc/kdeutils2 Makefile ports/net/kdenetwork2 Makefile ports/x11-clocks/kdetoys2 Makefile ports/x11/kde2 Makefile ports/x11/kdebase2 Makefile ports/x11/kdelibs2 Makefile ...
Message-ID:  <Pine.BSF.4.21.0007191535440.1745-100000@thelab.hub.org>
In-Reply-To: <20000719135827.P11216@argon.gryphonsoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Jul 2000, Will Andrews wrote:

> On Wed, Jul 19, 2000 at 10:50:48AM -0700, Satoshi Asami wrote:
> >   Modified files:
> >     converters/kdesupport2 Makefile 
> >     games/kdegames2      Makefile 
> >     misc/kdeutils2       Makefile 
> >     net/kdenetwork2      Makefile 
> >     x11-clocks/kdetoys2  Makefile 
> >     x11/kde2             Makefile 
> >     x11/kdebase2         Makefile 
> >     x11/kdelibs2         Makefile 
> >     editors/koffice      Makefile 
> >     x11-toolkits/kde-qt-addon Makefile 
> >   Log:
> >   Mark these BROKEN, they don't compile/run properly.
> >   
> >   Submitted by:	maintainer
> 
> Thank you.  That said, I am currently working on snapshot versions of
> these ports, and hope to commit them shortly after the release, so they
> can get some field testing.
> 
> Unfortunately, it requires Qt 2.2.0beta0, aka qt-copy, from the KDE
> repository.  I don't think qt-copy is suitable for replacement for qt21,
> so I'm wondering whether it would be permissible for a repo-copy from
> qt21 to qt22.  We can bump the shlib version if necessary.
> 
> OTOH, this is bleeding-edge beta software.  I could just post a place
> where I keep up-to-date KDE2 ports along with a qt-copy port, and do
> daily snap builds + logs etc., and post them there.
> 
> I think it would be better than putting it in the tree, primarily to
> avoid problems with people who don't know the situation and assume the
> ports in /usr/ports are well-tested etc. only to find out that 6-15
> hours of compiling got them nothing.  Also, to avoid the qt21 vs.
> qt-copy problem above.
> 
> I have already discussed this snapshot idea with scrappy, and it seems
> like the best way to go about this.

Just a quick thought here ... if all the kde2 stuff is marked as BROKEN,
would it be permissable for Will to merge his updates into there with a
BROKEN message of something like 'needs qt-copy, see http://(?) for
instructions'?

that way it requires those of us willing/able to help Will out to just
remove the BROKEN tag(s) to build?

Just a thought ...




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007191535440.1745-100000>