Discussion:
release preperations
Johannes Hofmann
2013-03-05 16:47:00 UTC
Permalink
Hi,
I've pushed a new script, which uses the text versions (and adds the
licence information as comments). Should it download directly from
CTAN? From mirrors.dotsrc.org? Ask for a mirror?
If mirrors.dotsrc.org works, that's probabely nicer - though I doubt
we create any significant load.
Mirrors.dotsrc.org works; I've changed the script. (Look at the
beginning.)
As for the way to inform the user, see attached patch, which will let
"make install" (and friends) print a message. Comments?
Nice, but most users will get precompiled packages from their
distributions.
How is the other work on the release going on? What is still missing?
I started a couple of times to add some lines to the man page that
explain how to get and install the pattern files, but never came up
with anything good. Should we copy the lines from your patch below?
How many people compiling dillo from the tarball are actually reading
README and the man page?
At least the man page get's installed with most binary packages.
I tried to include some info about the pattern files and how
they can be downloaded - please give it a review.
Also we would need to install the install-hyphenation script, so
that it becomes part of binary packages.
If we do that it would have to be renamed to
dillo-install-hyphenation or something like that.
Does this sound ok?

Cheers,
Johannes

PS: For me the documentation issue for hyphenation patterns is the
only thing left before we could make a release candidate, or am I
missing something?
Sebastian Geerken
2013-03-05 22:35:02 UTC
Permalink
Hi,

I hope I am, as the developer of hyphenation, not biased on this
topic. :-)
Post by Johannes Hofmann
As for the way to inform the user, see attached patch, which will let
"make install" (and friends) print a message. Comments?
Nice, but most users will get precompiled packages from their
distributions.
How is the other work on the release going on? What is still missing?
I started a couple of times to add some lines to the man page that
explain how to get and install the pattern files, but never came up
with anything good. Should we copy the lines from your patch below?
How many people compiling dillo from the tarball are actually reading
README and the man page?
At least the man page get's installed with most binary packages.
I tried to include some info about the pattern files and how
they can be downloaded - please give it a review.
"man dillo" shows

In order to use the hyphenation feature, pattern files from CTAN need
to be installed to ${prefix}/lib/dillo/hyphenation/. This can be done
with the script install-hyphenation. Call it with ISO-639-1 language
codes as arguments, or without arguments to get more help.

"${prefix}" should be replaced here.
Post by Johannes Hofmann
Also we would need to install the install-hyphenation script, so
that it becomes part of binary packages.
There would also some changes neccessary, since the script searches
"Makefile".

This is an aspect I have not yet thought about: whether the script is
part of the installation process (as now) or the installation itself
(as you suggest).
Post by Johannes Hofmann
If we do that it would have to be renamed to
dillo-install-hyphenation or something like that.
Does this sound ok?
I'd leave the question, how binary packages are handled, to the
maintainers of the binary packages, since they know best how to handle
this. (E. g., Debian provides packages texlive-lang-... for each
language.)

Perhaps package maintainers may comment on this.

OTOH, if someone installs dillo from the tarball, and does not notice
that she should download pattern files. Since hyphenation is inactive,
when there is no pattern file installed, this feature will be
invisible.

That's why I thought to put it into the Makefile, so he sees the
notice when he calls "make install". That's what I meant with my
question.

Sebastian
Johannes Hofmann
2013-03-06 20:57:36 UTC
Permalink
Post by Sebastian Geerken
Hi,
I hope I am, as the developer of hyphenation, not biased on this
topic. :-)
Post by Johannes Hofmann
As for the way to inform the user, see attached patch, which will let
"make install" (and friends) print a message. Comments?
Nice, but most users will get precompiled packages from their
distributions.
How is the other work on the release going on? What is still missing?
I started a couple of times to add some lines to the man page that
explain how to get and install the pattern files, but never came up
with anything good. Should we copy the lines from your patch below?
How many people compiling dillo from the tarball are actually reading
README and the man page?
At least the man page get's installed with most binary packages.
I tried to include some info about the pattern files and how
they can be downloaded - please give it a review.
"man dillo" shows
In order to use the hyphenation feature, pattern files from CTAN need
to be installed to ${prefix}/lib/dillo/hyphenation/. This can be done
with the script install-hyphenation. Call it with ISO-639-1 language
codes as arguments, or without arguments to get more help.
"${prefix}" should be replaced here.
Yes. Does someone know how this is best done with automake?
Post by Sebastian Geerken
Post by Johannes Hofmann
Also we would need to install the install-hyphenation script, so
that it becomes part of binary packages.
There would also some changes neccessary, since the script searches
"Makefile".
This is an aspect I have not yet thought about: whether the script is
part of the installation process (as now) or the installation itself
(as you suggest).
If we install it it will probabely end up in binary packages and be
available for end users.
If we don't install it, we rely on packagers to deal with the
problem (e.g. to create a separate hyphenation pattern package).
Post by Sebastian Geerken
Post by Johannes Hofmann
If we do that it would have to be renamed to
dillo-install-hyphenation or something like that.
Does this sound ok?
I'd leave the question, how binary packages are handled, to the
maintainers of the binary packages, since they know best how to handle
this. (E. g., Debian provides packages texlive-lang-... for each
language.)
Perhaps package maintainers may comment on this.
That would be really helpful.
Post by Sebastian Geerken
OTOH, if someone installs dillo from the tarball, and does not notice
that she should download pattern files. Since hyphenation is inactive,
when there is no pattern file installed, this feature will be
invisible.
That's why I thought to put it into the Makefile, so he sees the
notice when he calls "make install". That's what I meant with my
question.
We can of course also add the notice to make install, that should
not harm anyone.

Johannes
Sebastian Geerken
2013-03-06 21:28:34 UTC
Permalink
Post by Johannes Hofmann
Post by Sebastian Geerken
"man dillo" shows
In order to use the hyphenation feature, pattern files from CTAN need
to be installed to ${prefix}/lib/dillo/hyphenation/. This can be done
with the script install-hyphenation. Call it with ISO-639-1 language
codes as arguments, or without arguments to get more help.
"${prefix}" should be replaced here.
Yes. Does someone know how this is best done with automake?
Move doc/dillo.1 to doc/dillo.1.in and add this to doc/Makefile.am:

diff -r f37ab8cb8930 doc/Makefile.am
--- a/doc/Makefile.am Tue Mar 05 19:47:09 2013 +0100
+++ b/doc/Makefile.am Wed Mar 06 22:24:33 2013 +0100
@@ -39,3 +39,6 @@
Selection.txt \
Dpid.txt \
README
+
+dillo.1:
+ sed 's%.{prefix}%${prefix}%g' < dillo.1.in > dillo.1

This replaces ${prefix} by the actual value. I could not get the "$"
into the sed expression (therefore the "."), so this is not perfect.
Post by Johannes Hofmann
Post by Sebastian Geerken
Post by Johannes Hofmann
Also we would need to install the install-hyphenation script, so
that it becomes part of binary packages.
There would also some changes neccessary, since the script searches
"Makefile".
This is an aspect I have not yet thought about: whether the script is
part of the installation process (as now) or the installation itself
(as you suggest).
If we install it it will probabely end up in binary packages and be
available for end users.
If we don't install it, we rely on packagers to deal with the
problem (e.g. to create a separate hyphenation pattern package).
Post by Sebastian Geerken
Post by Johannes Hofmann
If we do that it would have to be renamed to
dillo-install-hyphenation or something like that.
Does this sound ok?
I'll try to modify the script, so it can be installed to
${prefix}/bin. In any case, this is certainly useful.
Post by Johannes Hofmann
[...]
Post by Sebastian Geerken
OTOH, if someone installs dillo from the tarball, and does not notice
that she should download pattern files. Since hyphenation is inactive,
when there is no pattern file installed, this feature will be
invisible.
That's why I thought to put it into the Makefile, so he sees the
notice when he calls "make install". That's what I meant with my
question.
We can of course also add the notice to make install, that should
not harm anyone.
Although I must admit that this approach only works for one message.

Sebastian
Johannes Hofmann
2013-03-06 22:20:34 UTC
Permalink
Post by Sebastian Geerken
Post by Johannes Hofmann
Post by Sebastian Geerken
"man dillo" shows
In order to use the hyphenation feature, pattern files from CTAN need
to be installed to ${prefix}/lib/dillo/hyphenation/. This can be done
with the script install-hyphenation. Call it with ISO-639-1 language
codes as arguments, or without arguments to get more help.
"${prefix}" should be replaced here.
Yes. Does someone know how this is best done with automake?
diff -r f37ab8cb8930 doc/Makefile.am
--- a/doc/Makefile.am Tue Mar 05 19:47:09 2013 +0100
+++ b/doc/Makefile.am Wed Mar 06 22:24:33 2013 +0100
@@ -39,3 +39,6 @@
Selection.txt \
Dpid.txt \
README
+
+ sed 's%.{prefix}%${prefix}%g' < dillo.1.in > dillo.1
This replaces ${prefix} by the actual value. I could not get the "$"
into the sed expression (therefore the "."), so this is not perfect.
Thanks, I pushed it.

Johannes
Sebastian Geerken
2013-03-08 13:40:04 UTC
Permalink
Post by Sebastian Geerken
Post by Johannes Hofmann
Post by Sebastian Geerken
Post by Johannes Hofmann
Also we would need to install the install-hyphenation script, so
that it becomes part of binary packages.
There would also some changes neccessary, since the script searches
"Makefile".
This is an aspect I have not yet thought about: whether the script is
part of the installation process (as now) or the installation itself
(as you suggest).
If we install it it will probabely end up in binary packages and be
available for end users.
If we don't install it, we rely on packagers to deal with the
problem (e.g. to create a separate hyphenation pattern package).
Post by Sebastian Geerken
Post by Johannes Hofmann
If we do that it would have to be renamed to
dillo-install-hyphenation or something like that.
Does this sound ok?
I'll try to modify the script, so it can be installed to
${prefix}/bin. In any case, this is certainly useful.
Done, plus some polishing. Call dillo-install-hyphenation either from
the tarball directory or from /usr/local/bin.

Sebastian
Jorge Arellano Cid
2013-04-04 17:32:02 UTC
Permalink
Hi,
Hi,
I won't be available next week. I think we could release 3.0.3 now.
So I would propose we work together to get it out today or tomorrow.
Alternatively you do it without me next week, or we wait unil I'm
back.
What do you think?
Johannes
PS: Jorge, would you be available to sign the final tarball?
Yes, I'm here with lots of other things to do, but I can
sign, or perhaps better, finish the process next week.
Thanks. It would be cool, if you and corvid could finish it.
Just reviewed the tarball and uploaded a small informational
patch to the repo. (plese check).

AFAICS the only pending thing is a mention of the new domainrc
filtering feature and to make sure "make install" or the packager
puts it in the right place.

@corvid: please check domainrc and add a small comment in the
"release overview" section of the splash page.

It looks more or less cooked now. The remaining things are mainly
in the web site.
--
Cheers
Jorge.-
Jorge Arellano Cid
2013-04-05 20:03:56 UTC
Permalink
Post by Jorge Arellano Cid
AFAICS the only pending thing is a mention of the new domainrc
filtering feature and to make sure "make install" or the packager
puts it in the right place.
@corvid: please check domainrc and add a small comment in the
"release overview" section of the splash page.
It looks more or less cooked now. The remaining things are mainly
in the web site.
Okay, I checked that domainrc is found and used after "make install",
and wrote a little something for splash. I added a quick mention to
user_help so they'll at least know it exists (would've liked to have
more than a sentence to put there, but it was as much as came to mind
at the moment)...
Good!

It looks like a good time to pack rc2.
--
Cheers
Jorge.-
corvid
2013-04-05 19:11:10 UTC
Permalink
Post by Jorge Arellano Cid
AFAICS the only pending thing is a mention of the new domainrc
filtering feature and to make sure "make install" or the packager
puts it in the right place.
@corvid: please check domainrc and add a small comment in the
"release overview" section of the splash page.
It looks more or less cooked now. The remaining things are mainly
in the web site.
Okay, I checked that domainrc is found and used after "make install",
and wrote a little something for splash. I added a quick mention to
user_help so they'll at least know it exists (would've liked to have
more than a sentence to put there, but it was as much as came to mind
at the moment)...

Loading...