Closed tumashu closed 7 years ago
Probably true! I kept thinking that I would finish Vcard import/export before I put it on elpa, but maybe that's not necessary. Plus I got distracted by some work on Gnus... I would like to get the manual finished and formatted correctly in Info format, but then I'll add it to the repos.
good news
I'm going to put this on ELPA soon. What do you think about separating the country libraries into separate packages? I imagine many people will only want to load the packages for the countries they're interested in. This would also reduce dependencies.
In my opinion, all ebdb extensions which depend non-elpa package should not be included into elpa, maybe melpa is a good place for these extension.
maybe we should split ebdb to:
It doesn't really matter whether a package is in elpa or melpa -- it's okay for elpa packages to depend on melpa packages. My only concern is, when users install EBDB, they shouldn't have to install a bunch of packages they will never use.
I like the idea of keeping all the ebdb-i18n-COUNTRY packages separate, that makes it a little more flexible. People can write and install whatever packages they like.
And yes, ebdb-company, ebdb-helm and ebdb-ivy would also be separate packages.
See the discussion on emacs.devel...
A way is: we just publish a ebdb package, when ebdb stable and someone want to split a country package to maintain, we just split it.
Everything's basically in place...
good job!!!
May be we should publish a beta version and add it to melpa, In my opinion, we need more tester....