Opened 14 years ago

Closed 14 years ago

#2413 closed task (fixed)

Add a note ogg123 can be built without curl

Reported by: laxy Owned by: Ag. Hatzimanikas
Priority: normal Milestone: 6.3
Component: BOOK Version: SVN
Severity: normal Keywords: ogg123
Cc:

Description

If you specify --without-curl ogg123 will be built, just without http streaming.

Currently BLFS gives the impression it can't be built without curl.

Attachments (1)

vorbis-tools_without_curl.diff (1.2 KB ) - added by Ag. Hatzimanikas 14 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 by Ag. Hatzimanikas, 14 years ago

Owner: changed from blfs-book@… to Ag. Hatzimanikas
Status: newassigned

I admit that this is the impression someone will get. But its quite difficult to mix in recommended dependencies..., required (libao) and yet not required but recommended? (cURL) dependencies in one row! and ... another thing and most important in my humble opinion that; when you are building ogg123 without cURL, you are loosing basic (expected nowadays) functionality. With two words: We can't list any possible switch and any possible combination in every package (it is an already complicated page).

Anyway, attached for review and suggestions, is a small patch that tries to address that issue. I added the switch in the 'Command Explanations' section, that allows ogg123 to be built without cURL. Of course with this way, I am waiting from the reader to read all the page down to that section, but to be honest I am not really sure how many of them will do that. I left the sed in the top of installation section, as it is harmless anyway, but again to be honest, a note about that sed was needed e.g, - apply that sed if you want to built ogg123- if we wanted to be accurate and consistent with the rest of the Book. So we have to try to keep this page simple as possible, as it's a simple package anyway.

by Ag. Hatzimanikas, 14 years ago

comment:2 by Ag. Hatzimanikas, 14 years ago

Resolution: fixed
Status: assignedclosed

Fixed in r7134.

Many thanks for the report.

Note: See TracTickets for help on using tickets.