All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Dreyer <kdreyer@redhat.com>
To: kefu chai <tchaikov@gmail.com>
Cc: ceph-maintainers@ceph.com,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: debian packaging for wip-10587-split-servers
Date: Fri, 10 Jul 2015 16:54:16 -0600	[thread overview]
Message-ID: <55A04D18.70202@redhat.com> (raw)
In-Reply-To: <CAJE9aOO5Wfxgtgvuj=Mx20C_ToVpY4VU37tS+7uGRbEjKZYEww@mail.gmail.com>

On 07/10/2015 08:21 AM, kefu chai wrote:
> can we
> - have another package named "ceph-base" which packages whatever ceph
> currently has now.
> - make the "ceph" a meta package which only offers the dependencies to
> ceph-mon, ceph-osd, ceph-mds? and let ceph-{mon,osd,mds} Depends on
> "ceph-base" instead?

I was hoping to avoid this route because it seemed complex, but the
further I dig on this, I think your suggestion is going to be the best
way forward.

So to re-state the plan: Files that are shared between multiple servers
will move into "ceph-base", and then:

For RPMs:
- "ceph-{mon,osd,mds}" Require: ceph-base.
- "ceph" will become a metapackage that Requires: ceph-{mon,osd,mds}.

For DEBs:
- "ceph-{mon,osd,mds}" will Depends: ceph-base.
- "ceph" will become a metapackage that Depends: ceph-{mon,osd}.
- "ceph" will continue to Recommends: ceph-mds

I've done some testing with a dummy package and this works. "apt-get
upgrade" kept the update back, since there were new packages introduced,
but "apt-get dist-upgrade" worked. Is that expected? (... newbie Debian
user here :D )

I've pushed this approach to
https://github.com/ceph/ceph/tree/wip-10587-split-servers.

- Ken

  reply	other threads:[~2015-07-10 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 15:57 debian packaging for wip-10587-split-servers Ken Dreyer
2015-07-10 14:21 ` kefu chai
2015-07-10 22:54   ` Ken Dreyer [this message]
2015-07-10 22:56     ` Ken Dreyer

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=55A04D18.70202@redhat.com \
    --to=kdreyer@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-maintainers@ceph.com \
    --cc=tchaikov@gmail.com \
    /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.