17625 – MySQL 4.0.x should not be masked in unstable

Bug 17625 - MySQL 4.0.x should not be masked in unstable

Summary: MySQL 4.0.x should not be masked in unstable

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal
Assignee:	Donny Davies (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-03-16 07:30 UTC by Steffen Weber
Modified:	2003-03-16 14:37 UTC (History)
CC List:	2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Steffen Weber 2003-03-16 07:30:27 UTC

As MySQL 4.0.x is quite usable right now I think it should no longer be masked, but 
instead marked as unstable so that it is only installed by default when having set the 
ACCEPT_KEYWORDS flag. 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Bjarke Istrup Pedersen (RETIRED) gentoo-dev

2003-03-16 12:37:07 UTC

I have to agree, it runs more stable then mysql-3.23.x does.

Comment 2 Donny Davies (RETIRED) gentoo-dev

2003-03-16 14:37:42 UTC

This report doesnt make sense.

> I think it should no longer be masked, but instead marked as unstable so that 

  It already *is* marked as unstable

> it is only installed by default when having set the ACCEPT_KEYWORDS flag

  It already *is* only installed by default if you want ~testing packages.

  Further, this is not released for production yet.  The most recent release
  in the tree is a "gamma" release.

  Also, you already know how to install it by either quelling package.mask
  or passing a full path to emerge.

  So no, it should still be in package.mask.