Re: Emacsen intermediate step proposal.

[Brian White <bcwhite@verisim.com>]

> > I know we already have an emacs package.  I use it.  It seems silly to create
> > a different virtual package name.  That will just create more problems with
> > any package that already have a dependancy on emacs.
> 
> And providing a virtual package will break any elisp packages that aren't
> expecting the new scheme.
> 
> > Also, I thought "Conflicts:" would stop coinstallation but "Replaces:" would
> > allow it.  Once the actual emacs package has been purged, the virtual package
> > should go unseen except when calculating dependancies.  It's transparent to
> > replace/conflict directives.  (I believe so, anyway.)
> 
> I slightly mistyped, if you conflict and replace emacs then nothing else
> providing emacs can install.  And since conflicting and replacing emacs is
> about the only way to get emacs19 to install cleanly, you've nicely
> removed any chance of using emacs as a virtual package name.

Perhaps having a non-clean install of emacs19 would be worth it to save
problems with other packages the already declare dependancies on emacs.

                                          Brian
                                 ( bcwhite@verisim.com )

-------------------------------------------------------------------------------
    In theory, theory and practice are the same.  In practice, they're not.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .