Bug 124389 (rekall)

Summary: [RFE] please include rekall in future releases
Product: [Fedora] Fedora Reporter: Ramiro Pereira <ramiro>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED DEFERRED QA Contact: Bill Nottingham <notting>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: rvokal, wtogami
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-26 19:44:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ramiro Pereira 2004-05-26 09:18:27 UTC
Rekall is a database front-end, somewhat in the style of MicroSoft®
Access(tm). However, Rekall is not itself a database, and does not
include a database. By this we mean that data is stored somewhere else
in an SQL server, and Rekall is fundementaly just a tool to extract,
display and update that data.
http://www.rekallrevealed.org/

Comment 1 Ed Bailey 2004-05-26 19:30:22 UTC
Moving to more appropriate component...

Comment 2 Bill Nottingham 2004-05-26 19:44:46 UTC
At this point, I don't think it will be added to Core - I'd make sure
it's in something like fedora.us first.