public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@cvs.gentoo.org>
Subject: AW: [gentoo-dev] gpm & mozilla bugs -- Suggestion for Portage extensions
Date: Thu Sep 20 07:51:01 2001	[thread overview]
Message-ID: <BLEMKJBINAFGJOKNKPIFAEMICBAA.sebastian@werner-productions.de> (raw)
In-Reply-To: <20010920153250.A32755@prosalg.no>

Isn't it possible to copy the files, which mozilla creates on the first
start as root.
We could add these files as patch to the mozilla archive. So we don't hae
the problem
to must start mozilla first. I like to have a system which works without to
much work
after installation...

Sebastian

-----Ursprungliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org]Im Auftrag von Karl Trygve
Kalleberg
Gesendet: Donnerstag, 20. September 2001 15:33
An: gentoo-dev@cvs.gentoo.org
Betreff: Re: [gentoo-dev] gpm & mozilla bugs -- Suggestion for Portage
extensions


On Thu, Sep 20, 2001 at 10:52:34AM +0200, Mikael Hallendal wrote:
> tor 2001-09-20 klockan 01.46 skrev Morgan Christiansson:
>
> Hi!
>
> > *mozilla-0.9.3 segfaults when started as  non-root, mozilla-bin-0.9.4
> > doesn't work either.
>
> Hmm, you have to first start mozilla as root (once after install), then
> it should be fine to run it as any user.

The ebuild should inform the user of this caveat.

In fact, we should have some kind of global notices for the portage
system. When an ebuild has required or suggested post-install steps, these
should be added to the notices list.

The user would then do:
# notices
to list all notices
# notices mozilla
to list all notices pertaining to mozilla
# notices --del mozilla
to delete all notices pertaining to mozilla

For very many packages, it would be nice for the user to have an archive
of required, manual post-install steps. The entry in the notices list may
be a complete step-by-step howto for trivial stuff, or a reference to a
real howto on our website.

It might be of interest to be able to mark notices as done, but still be
able to bring them back at a later stage, when one wants to reconfigure a
package.

# notices --purge <ebuild>
will delete the notices for good
# notices --del <ebuild>
will just remove it from the list of active notices
# notices --undel <ebuild>
will reinstate the notice


In other distros, (Debian), required manual intervention in the
post-install step is covered by the apt's menu-system. We might not want
to do this, leaving the details and timing to the user.


Karl T


_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev




  parent reply	other threads:[~2001-09-20 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19 17:48 [gentoo-dev] gpm & mozilla bugs Morgan Christiansson
2001-09-19 22:51 ` Martin Schlemmer
2001-09-20  2:53 ` Mikael Hallendal
2001-09-20  7:39   ` [gentoo-dev] gpm & mozilla bugs -- Suggestion for Portage extensions Karl Trygve Kalleberg
2001-09-20  7:47     ` Mikael Hallendal
2001-09-20 14:30       ` Karl Trygve Kalleberg
2001-09-20  7:51     ` Sebastian Werner [this message]
2001-09-20  7:58       ` AW: " Mikael Hallendal
2001-09-20 10:00         ` AW: AW: [gentoo-dev] gpm & mozilla bugs -- Suggestion for Portageextensions Sebastian Werner

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=BLEMKJBINAFGJOKNKPIFAEMICBAA.sebastian@werner-productions.de \
    --to=sebastian@werner-productions.de \
    --cc=gentoo-dev@cvs.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