From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 299] New: add shared-mime-info package
Date: Thu, 23 Apr 2009 10:58:06 +0000 (UTC) [thread overview]
Message-ID: <bug-299-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=299
Summary: add shared-mime-info package
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P4
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: s.neumann at phase-zero.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
The shared-mime-info package contains the core database of common types and the
update-mime-database command used to extend it.
The attached files and patches add the shared-mime-info package to buildroot.
The only thing that is actually needed in the target is the file mime.cache. In
order to generate that file, shared-mime-info is installed into the
staging-dir. The idea is that other packages might add more mime-info files and
these should be collected in staging-dir. From there the mime.cache file is
created using tools installed in host-dir and copied to target.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-04-23 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 10:58 bugzilla at busybox.net [this message]
2009-04-23 10:59 ` [Buildroot] [Bug 299] add shared-mime-info package bugzilla at busybox.net
2009-04-23 11:07 ` bugzilla at busybox.net
2009-04-23 11:08 ` bugzilla at busybox.net
2009-04-23 11:24 ` bugzilla at busybox.net
2009-04-28 9:48 ` bugzilla at busybox.net
2009-04-28 22:05 ` bugzilla at busybox.net
2009-04-29 7:29 ` bugzilla at busybox.net
2009-04-29 7:59 ` bugzilla at busybox.net
2009-04-29 8:38 ` bugzilla at busybox.net
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=bug-299-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.