El 04/01/2016 a las 12:29, Kevin Brubeck Unhammer escribió: > [...] > >> But I am not sure what is the convention in this case, as there is a >> change in the name (apertium-es-an to apertium-spa-arg), and probably >> each monolingual package should have a new release. Also, I guess the >> predecessor trunk/apertium-es-an/ directory should go from the trunk to >> some other place in order not to confound users. So, I would be very >> happy if someone else could take care of tagging this release and >> putting everything where it should be. >> >> The release notes have been updated in >> http://sourceforge.net/p/apertium/svn/64371/ > Is 64371 the revision that should be the release for both arg, spa and > spa-arg? (I can do the formalities.) Great! Better 64372, where I changed the dates in AUTHORS.
> > I think trunk/apertium-es-an should be deleted, if all that's useful > From it is moved to spa-arg – it'll be available in the SVN history > anyway. Ok [...] >> Also, I am concerned about users of apertium-es-an realizing that the >> new version of the package is now apertium-spa-arg, with a different >> installation method. Is there some way to redirect them to the new package? > I think it's possible to have "aliases" at least for apt, e.g. if I try > installing "apertium-nob-nno", apt-get tells me > > Note, selecting 'apertium-nno-nob' instead of 'apertium-nob-nno' > > So that ought to work for es-an as well. > Fine, that should be then done for apertium-es-an, where are these aliases defined? This will be needed for more pairs if pairs are moving progressively from two-letter to three-letter codes. thanks, Juan Pablo ------------------------------------------------------------------------------ _______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
