Opened 13 years ago

Closed 13 years ago

#2262 closed Enhancement (invalid)

create a --enable-web switch

Reported by: sahko Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.72
Severity: Normal Keywords:
Cc:

Description

It would be very handy if there was a build time option to disable the web interface, many people have no use for. Just like it happens with gtk, cli , daemon etc. Thanks

Change History (9)

comment:1 follow-up: Changed 13 years ago by livings124

  • Milestone changed from 1.73 to None Set
  • Resolution set to invalid
  • Status changed from new to closed

Don't set milestones if you're not submitting a patch.

I see no reason to add/remove individual features if they're not being used. Removing it wouldn't give much benefit.

comment:2 in reply to: ↑ 1 Changed 13 years ago by mezz

Replying to livings124:

I see no reason to add/remove individual features if they're not being used. Removing it wouldn't give much benefit.

Maybe you don't see any benefit, but it does benefit for the packages. This will allowing us to be able to install seperate packages of gtk and daemon without have conflict to the each others or double files. Current, I have a custon patch to disable web for gtk and daemon packages in FreeBSD then create a transmission-web package. That way; gtk and daemon can depend on web without have double or overwrite the web files.

comment:3 Changed 13 years ago by charles

mezz: wouldn't it make more sense to have a libtransmission package that has the core libtransmission library + libnatmpmp + minupnpc + libdht + the web files?

comment:4 Changed 13 years ago by charles

  • Resolution invalid deleted
  • Status changed from closed to reopened

comment:5 Changed 13 years ago by mezz

The web is a client, so I don't think it fits in core? Honestly, I don't know what to say about this because I am very flexible with that kind of issue (seperate library and client).

I only responed to this ticket because I liked the idea of --enable-web and it makes sense to have it. What if the users (I am one of them on other machines) only want to install transmissioncli, so do they really need to have the web files? :-)

comment:6 Changed 13 years ago by charles

mezz: if I were going to split up the packages -- which will probably eventually happen at the tarball level -- I'd put clutch, libdht, miniupnpc, libnatpmp, and libtransmission together in a libtransmission package.

The gtk client needs all of those pieces in order to work

The qt client needs all of those pieces on order to work

The daemon needs all of those pieces in order to work

The cli client needs all of those, except arguably the web files, in order to work

For simplicity's sake IMO it makese sense to bundle all those pieces together...

comment:7 Changed 13 years ago by mezz

Sounds good to me. When you create a libtransmission tarball. Are you going to add transmission.pc or transmission-1.0.pc file?

comment:8 Changed 13 years ago by charles

When that happens, yes there'll definitely be a .pc file. However I'm not saying this is happening anytime soon -- just telling you what the Long Term plans are, in case that affects how you want to do your packaging now.

comment:9 Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.