[Pkg-ime-devel] The upstream devlopment of SCIM packages

Ming Hua minghua@rice.edu
Fri, 28 Jan 2005 12:52:12 -0600


On Fri, Jan 28, 2005 at 07:46:40AM +0100, Osamu Aoki wrote:
> On Thu, Jan 27, 2005 at 11:25:41PM -0600, Ming Hua wrote:
> > On Sun, Jan 23, 2005 at 07:28:33PM +0100, Osamu Aoki wrote:
> > > On Sat, Jan 22, 2005 at 11:21:34PM -0600, Ming Hua wrote:
> > > > The imengine plugin for scim-tables will be separated from scim and put
> > > > into scim-tables package.  This means we can't have a arch:all package
> > > > for scim-tables anymore.  Most likely I am going to add a arch:any
> > > > scim-imengine-table package to the scim-tables source package.
> > > 
> > > You mean to keep arch:all part to be binary scim-tables package and add
> > > binary scim-imengine-table package.  THat sounds good to me.
> > 
> > Yes that is what I meant, a binary package scim-tables-bin, for example.
> 
> Or scim-tables-common  (Some package use this too.  Emacs is the only
> with one -bin-common .)

Hmm, I was under the impression that -common is a arch:all package along
with other arch:any packages in the same source package, not vise versa.
However it doesn't seem to be the consensus.  Anyway on second thought,
I am inclined with the name scim-imengine-table.  Let's leave this
detail for later. :-)

Ming
2005.01.28