Re: [AUCTeX-devel] Plan for a new release? [Was: preview.sty included in GNU ELPA problematic]

[Mosè Giordano]

Hi Tassilo and other co-maintainers,

for the release process we should follow the "Distributions" section
of the GNU Maintainer guide, right?  I can build and sign all
tarballs, including XEmacs and Windows ones, but who will send the
packages to the FTP server?  For what is worth, I haven't gone through
the process to automate FTP uploads yet.

In the Makefile, the default shell is a generic /bin/sh, but in the
release-sign rule there is a "read -sp" command which is, AFAIK,
specific to "bash" and /bin/sh doesn't necessarily points to bash (in
Debian and derivates it doesn't).  The "-p" option can be replaced by
a preceding "echo -n" message, the "-s" option doesn't have a generic
replacement.  A solution could be to set the shell to /bin/bash,
another could be to replace the read "-p" option with the "echo" and
drop the "-s" option.

Bye,
Mosè


2014-08-06 20:45 GMT+02:00 Tassilo Horn <address@hidden>:
> Mosè Giordano <address@hidden> writes:
>
> Hi Mosè,
>
>> how about the first week of September to roll the new release?  We
>> would have another month of testing.
>
> Fine with me!
>
> Bye,
> Tassilo
>
>>> Mosè Giordano <address@hidden> writes:
>>>
>>>>> I should be able to build the XEmacs package, now that it can be
>>>>> compiled without errors, but I don't use Windows.
>>>>
>>>> I confirm I succeed in building the XEmacs package, using XEmacs
>>>> 21.4.22.
>>>
>>> Perfect.
>>>
>>>> I've just pushed to the repository a change which removes .cvsignore
>>>> and the tests directory from the tarball.  Since the files to be
>>>> included in the tarball are retrieved with `git archive', a
>>>> .gitattributes file should do the job as well, but I preferred to keep
>>>> doing it inside inside the Makefile instead of adding a new file to
>>>> the project.
>>>
>>> Yes, I also prefer to have everything in one central place.
>>>
>>> Thanks a lot,
>>> Tassilo
>>>
>