public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: Wed, 26 Dec 2001 08:39:38 +0200	[thread overview]
Message-ID: <200112260644.ADS86564@odin.inter.net.il> (raw)
In-Reply-To: <20011225234317.G17475@chiba.3jane.net>

On Wednesday 26 December 2001 07:43, you wrote:
> On Wed, Dec 26, 2001 at 05:10:11AM +0100, Mikael Hallendal wrote:
> > Ok, looks like you misunderstood me. I'm not talking about beta
> > _ebuilds_. I'm talking about beta packages (like for instance, GNOME
> > produces lots of beta releases of GNOME2. These packages are _only_
> > supposed for GNOME developers). From my discussion with Dan about this
> > issue, the KDE3 betas we are discussing here are for KDE developers.
Well, actually they're for developers and beta-testers. And quite a lot of 
people are in that second category - for example back in the pre-KDE-2.0 days 
I used suse. And in suse 7.0 they included both the latest stable kde 1.x, 
and the latest 2.0 beta. And they regularly released rpms on their update 
website for the latest kde 2.0 betas/rcs, and as I remember it worked out OK 
- suse forums weren't swamped with problems caused by beta packages; most 
users correctly directed those to kde. 

>
> OK; if Dan is just adding KDE3 beta stuff just to have it around, it's a
> waste of time.  If he needs it around to get ready for KDE3 himself, then I
> see some merit.  I think Dan may just be getting a little overzealous and
> wanting to add it just because it's there.
Well, as for myself, I'm working on kde3 ebuilds because I really need the 
new Hebrew support. Right now I'm forced to use msoffice under vmware with 
kde 2.x. As soon as kde3 is stable enough, and it should be by now, I'll 
switch to using it for my day-to-day work. And of course, being the kde 
packager, I naturally want to create ebuilds and share them.

> I don't anticipate that KDE3
> will be particularly hard to build.
It's not - it's just as easy as kde2. The only thing that's difficult is the 
kde2/3 coexistence with its various demands.

>
> So, I finally agree with you :)  Dan, I think it's bad policy to add KDE3
> beta ebuilds just for the sake of having them.  I would only add them if we
> actually have requests from KDE developers who happen to use Gentoo Linux. 
> But I imagine that any red-blooded KDE developers would be grabbing their
> stuff from CVS anyway.
Well, I understand that. And I started this thread asking for advice on where 
to put my ebuilds (outside Gentoo) for those who do want to use them and/or 
help me work on them. That question remained unanswered btw.

Of course it'd have been more comfortable for me to have them in cvs & 
masked, but I understand Hallski's concerns and I'm willing to go along with 
his decision, even if I don't agree.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel



  reply	other threads:[~2001-12-26  6:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22 16:57 [gentoo-dev] ebuilds for kde3 beta etc Dan Armak
2001-12-22 17:28 ` Daniel Robbins
2001-12-22 18:00   ` Dan Armak
2001-12-22 18:29     ` Guido Bakker
2001-12-22 18:12       ` Dan Armak
2001-12-23 13:44         ` Mikael Hallendal
2001-12-23 14:07           ` Dan Armak
2001-12-23 23:08             ` Mikael Hallendal
2001-12-24  0:36               ` Daniel Robbins
2001-12-24  8:27               ` Geert Bevin
2001-12-25  1:12                 ` Mikael Hallendal
2001-12-25  5:00                   ` Dan Armak
2001-12-25  5:11                     ` Daniel Robbins
2001-12-25 12:10                       ` Mikael Hallendal
2001-12-25 15:49                         ` Daniel Robbins
2001-12-25 20:19                           ` Mikael Hallendal
2001-12-25 20:40                             ` Geert Bevin
2001-12-26  1:47                               ` Daniel Robbins
2001-12-26  2:14                                 ` Mikael Hallendal
2001-12-26  2:44                                   ` Daniel Robbins
2001-12-26  3:01                                     ` Mikael Hallendal
2001-12-26  3:33                                       ` Daniel Robbins
2001-12-26  4:10                                         ` Mikael Hallendal
2001-12-26  5:43                                           ` Daniel Robbins
2001-12-26  6:39                                             ` Dan Armak [this message]
2001-12-26  6:51                                               ` Mikael Hallendal
2001-12-26  6:56                                                 ` Joshua Pierre
2001-12-27 19:41                                               ` Damon M. Conway
2001-12-26  5:16                               ` Joshua Pierre
2001-12-26  1:51                             ` Daniel Robbins
2001-12-24  9:59               ` Guido Bakker
2001-12-24 12:11                 ` Sebastian Werner
2001-12-24 13:38                   ` Dan Armak
2001-12-25  1:14                   ` Mikael Hallendal
2001-12-23 14:13   ` Dan Armak
2001-12-26  9:34     ` Dan Armak
2001-12-26  9:37     ` Dan Armak
2001-12-26 13:46       ` Bart Verwilst
2001-12-26 16:50         ` Daniel Robbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200112260644.ADS86564@odin.inter.net.il \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox