[Dillo-dev]RPM question, and how close is 0.8.0?
At 08:21 AM 2/3/2004, Jorge Arellano Cid wrote:
I'll start working on it after the 0.8.0 release.
Any idea how soon that's coming? I've started making the necessary changes for the RPM spec based on the current CVS version. With luck I'll be able to start building as soon as the tarball is ready. I've posted some test RPMs at http://www.hyperborea.org/software/dillo/pre.html if anyone's interested. Question: I noticed that several of the included DPIs (https, ftp, download) require wget. However, the main browser does not require wget. That leads to several choices as far as RPM dependencies go: 1. Include all DPIs in the dillo package. Don't require wget. 2. Include all DPIs in the dillo package. Do require wget. 3. Separate the FTP, HTTPS, and download DPIs into a separate package (something like "dillo-protocols") and set that package to require wget. Advantages: #1: Simple installation, most linux distros probably already include wget #2: Simple installation, lets you know about wget if you haven't installed it already. #3: If you don't want wget, you're not forced to install it. If you want the plugin, you're told wget is needed. Problems: #1: If you don't have wget, installing won't tell you that you need it. #2: If you don't want to use those DPIs and you don't want wget, you need to install it anyway. #3: Installing is more complicated, because you have to download and upgrade two RPMs. I don't think #1 is really an option, because it means people can install dillo via RPM and not everything will work. I'm inclined to choose #2 over #3, just because of the simplicity. If someone just wants to install Dillo, they already have to look through a list of about 10 different RPMs for the right system, and sometimes people miss the one they need. I occasionally get requests to add an RPM for a system that's already on the list. On the other hand, some people might consider wget to be unnecessary if they're not going to be using those DPIs. Anyway, has anyone got any thoughts on this issue? Kelson Vibber www.hyperborea.org
Hi Kelson! On Tue, 3 Feb 2004, Kelson Vibber wrote:
At 08:21 AM 2/3/2004, Jorge Arellano Cid wrote:
I'll start working on it after the 0.8.0 release.
Any idea how soon that's coming?
The idea is to have it ready this Sunday so the announcement is made by Monday in the morning. The newest CVS has the splash screen (grammar corrections are welcome:), and the pending issues are: * dpis should be able to run from ~/.dillo. I'll check that and maybe provide a shell script to install them there for users not having root access. * pthreads is still linked in dpis. This needs a patch but it's not indispensable. The release will be made with or without it. * Maybe it'd be good to mute dpid when started by dillo (to avoid printing to the terminal, specially when it exits). Not sure though and it's also a minor thing. * Expect reports on portability. This has been done to a good extent so I'll not delay the release because of it. After the release I'll take a week off! :-)
I've started making the necessary changes for the RPM spec based on the current CVS version. With luck I'll be able to start building as soon as the tarball is ready. I've posted some test RPMs at http://www.hyperborea.org/software/dillo/pre.html if anyone's interested.
Question: I noticed that several of the included DPIs (https, ftp, download) require wget. However, the main browser does not require wget. That leads to several choices as far as RPM dependencies go:
1. Include all DPIs in the dillo package. Don't require wget. 2. Include all DPIs in the dillo package. Do require wget. 3. Separate the FTP, HTTPS, and download DPIs into a separate package (something like "dillo-protocols") and set that package to require wget.
Advantages: #1: Simple installation, most linux distros probably already include wget #2: Simple installation, lets you know about wget if you haven't installed it already. #3: If you don't want wget, you're not forced to install it. If you want the plugin, you're told wget is needed.
Problems: #1: If you don't have wget, installing won't tell you that you need it. #2: If you don't want to use those DPIs and you don't want wget, you need to install it anyway. #3: Installing is more complicated, because you have to download and upgrade two RPMs.
I don't think #1 is really an option, because it means people can install dillo via RPM and not everything will work.
I'm inclined to choose #2 over #3, just because of the simplicity. If someone just wants to install Dillo, they already have to look through a list of about 10 different RPMs for the right system, and sometimes people miss the one they need. I occasionally get requests to add an RPM for a system that's already on the list. On the other hand, some people might consider wget to be unnecessary if they're not going to be using those DPIs.
Anyway, has anyone got any thoughts on this issue?
Just as you, my choice is #2. Cheers Jorge.-
At 06:14 AM 2/5/2004, Jorge Arellano Cid wrote:
The idea is to have it ready this Sunday so the announcement is made by Monday in the morning.
OK! Sooner than I expected! I may be busy this Sunday evening, but I'll at least build the source RPM and the RH8/RH9/FC1 RPM so they'll be ready on Monday. I'll add anything else I have time for, and do the rest Monday evening. (SuSE 9 will have to wait until Monday since I need to build it at work.)
2. Include all DPIs in the dillo package. Do require wget. ... Just as you, my choice is #2.
Sounds good. I'll do that. Kelson Vibber www.hyperborea.org
participants (2)
-
Jorge Arellano Cid -
Kelson Vibber