public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] macos mess
Date: Sat, 24 Jul 2004 19:56:47 -0400	[thread overview]
Message-ID: <200407241956.47777.vapier@gentoo.org> (raw)
In-Reply-To: <8DD1D809-DDC9-11D8-B5A6-000D93283962@gentoo.org>

On Saturday 24 July 2004 07:31 pm, Pieter Van den Abeele wrote:
> I've changed my mind. I'm not going to change the virtual file
> semantics in the MacOS profiles to get repoman to stop complaining.
> Instead I wrote a small (4 lines) patch for repoman which does the
> folowing:
>
> When repoman detects a macos-specific unsatisfied dependency it will
> check the packages.build file

that's a pretty ugly hack

are you suggesting we do this with every new random arch we add that isnt a 
standard linux port ?  seems like an unintuitive workaround

why not push something a little more intelligent ... perhaps a new file for 
portage to utilize in cases like this ... the profile has a special file 
where you can define packages that are assumed to be satisified
-mike

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-24 23:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 11:34 [gentoo-dev] macos mess Michael Sterrett -Mr. Bones.-
2004-07-24 16:54 ` Pieter Van den Abeele
2004-07-24 16:59   ` Mike Frysinger
2004-07-24 17:58     ` Travis Tilley
2004-07-24 18:36     ` Pieter Van den Abeele
2004-07-24 19:10       ` Mike Frysinger
2004-07-24 19:24       ` Pieter Van den Abeele
2004-07-24 19:30         ` Mike Frysinger
2004-07-24 19:58           ` Pieter Van den Abeele
2004-07-24 23:31             ` Pieter Van den Abeele
2004-07-24 23:56               ` Mike Frysinger [this message]
2004-07-25  0:21                 ` Pieter Van den Abeele
2004-07-24 20:54   ` Joshua Brindle
2004-07-24 22:30     ` Mike Frysinger
2004-07-24 23:18     ` Pieter Van den Abeele
2004-07-24 23:30       ` Mike Frysinger
2004-07-24 23:51         ` Pieter Van den Abeele
2004-07-24 23:58           ` Ciaran McCreesh
2004-07-25  0:25             ` Pieter Van den Abeele
2004-07-25  0:03           ` Pieter Van den Abeele
2004-07-25  0:34       ` Donnie Berkholz
2004-07-25  1:28         ` Jason Stubbs
2004-07-25 15:53         ` Alastair Tse
2004-07-25 19:57           ` Donnie Berkholz
2004-07-26  0:07             ` [gentoo-dev] Re: New drivers category in portage (Was [gentoo-dev] macos mess) Daniel Ostrow
2004-07-25 21:38               ` Gavin
2004-07-26  1:57                 ` Donnie Berkholz
2004-07-26  2:46                   ` [gentoo-dev] Re: New drivers category in portage (Was[gentoo-dev] " Gavin
2004-07-25  1:26   ` [gentoo-dev] macos mess Jason Stubbs
2004-07-25  2:22     ` Pieter Van den Abeele
2004-07-25  2:50       ` Jason Stubbs
2004-07-25  3:38         ` Pieter Van den Abeele
2004-07-25  4:42           ` Jason Stubbs
2004-07-25  5:40             ` Mike Frysinger
2004-07-25 11:36               ` Pieter Van den Abeele
2004-07-25  8:25             ` Jason Stubbs
2004-07-25  8:48               ` Jason Stubbs
2004-07-25 11:39               ` Pieter Van den Abeele
2004-07-25 11:30             ` Pieter Van den Abeele
2004-07-25 12:14               ` Jason Stubbs
2004-07-25 13:19                 ` Jason Stubbs

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=200407241956.47777.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.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