All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 241] New: device mapper + lvm2: build together
Date: Mon, 30 Mar 2009 19:53:03 +0000 (UTC)	[thread overview]
Message-ID: <bug-241-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=241

              Host: i686-linux
            Target: i686-linux
             Build: i386-pc-linux-gnu
           Summary: device mapper + lvm2: build together
           Product: buildroot
           Version: unspecified
          Platform: PC
               URL: http://lists.busybox.net/pipermail/buildroot/2009-
                    March/026345.html
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: razzor at kopf-tisch.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=207)
 --> (https://bugs.busybox.net/attachment.cgi?id=207)
[PATCH] device mapper + lvm2: build together

Both packages are merged upstream and are now build from one source tree.
- bump lvm2 version to 2.02.44 (contains device-mapper 1.02.30)
- fix bogous linking of ncurses when no readline support is found
- add uninstall target
- copy default config to /etc/lvm
- always build whole package but split install into two parts (device mapper
and lvm2 suite)
- let all packages that selected "dm" now select "lvm2"
- remove package dm


-- 
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.

             reply	other threads:[~2009-03-30 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 19:53 bugzilla at busybox.net [this message]
2009-06-20  6:25 ` [Buildroot] [Bug 241] device mapper + lvm2: build together 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-241-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.