public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] KDE split ebuilds
Date: Thu, 17 Mar 2005 21:03:11 +0200	[thread overview]
Message-ID: <200503172103.21556.danarmak@gentoo.org> (raw)
In-Reply-To: <4238A9AA.1000800@pnpitalia.it>

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

On Wednesday 16 March 2005 23:48, Francesco Riosa wrote:
> one question only:
> one of the point in having a splitted kde was that it make not necessary
> upgrade all kde because of a update of a single program.
> How do you can achive this mantaining all the packages at the same version?
> maybe with -r? versioning ?
If eg konqeror isn't updated in 3.4.1, only the 3.4.0 ebuild will exist. Doing 
an emerge kdebase-meta on a clean system will then install some packages at 
version 3.4.1, and some (like konqueror) at 3.4.0.

It takes some code to maintain the proper deps for this, but a lot less than 
for the general case propose by the OP.

-- 
Dan Armak
Gentoo Linux developer (KDE)
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-17 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 19:25 [gentoo-dev] KDE split ebuilds Tom Wesley
2005-03-16 19:49 ` Sven Vermeulen
2005-03-16 20:29 ` Dan Armak
2005-03-16 21:48   ` Francesco Riosa
2005-03-17 19:03     ` Dan Armak [this message]
2005-03-16 22:07   ` Tom Wesley
2005-03-16 22:17     ` Graham Murray
2005-03-17 19:11     ` Dan Armak
2005-03-17 19:13       ` Tom Wesley
2005-03-18 16:21   ` [gentoo-dev] " Duncan
2005-03-19 16:26     ` Dan Armak

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=200503172103.21556.danarmak@gentoo.org \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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