Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 92957 - Pugs 6.3.2 lacks an ebuild
Summary: Pugs 6.3.2 lacks an ebuild
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All All
: High normal
Assignee: Michael Cummings (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-17 10:56 UTC by Nathan Mahon
Modified: 2005-05-18 14:38 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Mahon 2005-05-17 10:56:19 UTC
according to my testing, it'll work fine if the DEPEND "virtuals/ghc" is changed
to "|| ( >=dev-lang/ghc-bin-6.4 >=dev-lang/ghc-6.4 )"


Reproducible: Always
Steps to Reproduce:
1.ls portage/dev-lang/pugs

Actual Results:  
only found 6.0.11

Expected Results:  
-rw-r--r--  1 root root    643 May 17 11:23 pugs-6.2.3.ebuild


version bug requested by mcummings.
Comment 1 Duncan Coutts (RETIRED) gentoo-dev 2005-05-18 03:56:02 UTC
I believe the perl herd usually deal with pugs, reassigning.
If this is not right, you can assign it back to us!
Comment 2 Michael Cummings (RETIRED) gentoo-dev 2005-05-18 14:21:27 UTC
Actually, folks on the haskell team asked that it be changed from the or  
statement to the virtual since the affect was the same (both packages provide  
the virtual). Were there problems with the virtual? Also, since 6.3.2 is some 
ways off (6.2.3 was just posted a few days ago), I have posted that instead for 
now. ;) 
Comment 3 Michael Cummings (RETIRED) gentoo-dev 2005-05-18 14:33:04 UTC
marking fixed since its in the tree. open a new bug for 6.3.2 when it really 
exists :) 
Comment 4 Andres Loeh (RETIRED) gentoo-dev 2005-05-18 14:38:03 UTC
We've had some discussion over at #88362 about the virtuals vs. || (...).

I'm currently experimenting with a switch to || (...)-style dependencies for all 
Haskell-related ebuilds, but I'm not fully convinced yet that this solves all
the problems for all packages.

Until we switch to a different solution for the Haskell packages in general,
I'd prefer all of them to use the same mechanism (which is the
virtual-dependency at the moment). Since you are the current maintainer, it
is, however, your call :)

ks