public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marko Mikulicic <marko@seul.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] doinst recursive?
Date: Tue, 04 Jun 2002 15:45:26 +0200	[thread overview]
Message-ID: <3CFCC476.9010308@seul.org> (raw)
In-Reply-To: 200206041508.22305.pauldv@cs.kun.nl

Paul de Vrieze wrote:
> On Tuesday 04 June 2002 14:42, Marko Mikulicic wrote:
> 
>>Dan Naumov wrote:
>>
>>>There is no real difference between an updated 1.1a system and a 1.2
>>>system. Also, this problem with acroread is a known bug. Do a search for
>>>it on Gentoo Bugzilla.
>>
>>Thank you. I cannot find the bug report.
>>However I wish to know one thing:
>>  "doins" will install its arguments. can it do it recursively, with
>>some switch. Where can I find the sources of the "doins" function ?
>>
>>thanks,
>>
> 
> /usr/lib/portage/bin/doins
> 
> Paul
> 
> ps the bug is allready resolved
> 

thanks.

I tried emerge rsync. Shall I use emerge cvs to get
the bugfix?

I'm curious to see how it is fixed, but I don't want to load unstable code.

Sorry for the stupid questions. I want to start as quick as possible
to write ebuild scripts for many little programs out there.

Thanks for the patience.

Marko



  reply	other threads:[~2002-06-04 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 12:06 [gentoo-dev] doinst recursive? Marko Mikulicic
2002-06-04 12:21 ` Dan Naumov
2002-06-04 12:42   ` Marko Mikulicic
2002-06-04 13:08     ` Paul de Vrieze
2002-06-04 13:45       ` Marko Mikulicic [this message]
2002-06-04 14:00         ` Dan Naumov
2002-06-04 14:16           ` Marko Mikulicic
2002-06-04 14:22             ` Grant Goodyear
2002-06-04 14:41               ` Marko Mikulicic
2002-06-04 14:46                 ` Marko Mikulicic

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=3CFCC476.9010308@seul.org \
    --to=marko@seul.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