public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: [gentoo-portage-dev] [Fwd: Re: GLEP: Making updates never break dependencies]
Date: Sat, 08 Nov 2003 13:26:29 -0500	[thread overview]
Message-ID: <1068315988.16010.2.camel@green> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 45 bytes --]


-- 
Grant Goodyear <g2boojum@gentoo.org>

[-- Attachment #1.2: Forwarded message - Re: GLEP: Making updates never break dependencies --]
[-- Type: message/rfc822, Size: 3818 bytes --]

[-- Attachment #1.2.1.1: Type: text/plain, Size: 1376 bytes --]

>  I just wrote a GLEP, proposing a solution to the problem that updating
>  f.ex. openssl, requires recompiling almost world
>  (kde,mozilla,galeon,wget,irrsi,python etc.) - and breaks your system if
>  you don't complete all this, while you are running (since the old
>  openssl files are removed after the openssl upgrade -and programs that
>  haven't been recompiled will break).

Dear Mr. Klavsen,
  Thank you very much for submitting this GLEP. I think it may need a
bit of work before we can accept it, however. A minor point is that we
request that GLEPs be written in a formal manner (no abbreviations such
as "f.ex", spelling should be checked, sentences should be complete,
subject and predicate should agree in number, etcetera). The more
substantive comment is that this GLEP raises a number of issues that I
think the GLEP itself should address: who will be making the required
portage changes, how would these changes impact developers, how
extensive would those changes be, how would these changes impact
performance, are there other alternative solutions to this problem that
should be considered, would the introduction of "reverse-dependencies"
solve this problem?  I've CC'd carpaski, the Gentoo Portage lead, in
case he might have additional comments.

Sincerely,
Grant Goodyear
GLEP Editor
-- 
Grant Goodyear <glep@gentoo.org>

[-- Attachment #1.2.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-11-08 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 18:26 Grant Goodyear [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08 18:32 [gentoo-portage-dev] [Fwd: Re: GLEP: Making updates never break dependencies] Grant Goodyear

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=1068315988.16010.2.camel@green \
    --to=g2boojum@gentoo.org \
    --cc=gentoo-portage-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