Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#38241 closed submission (fixed)

New port: quassel

Reported by: macports@… Owned by: neverpanic (Clemens Lang)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: quassel

Description

Port description: Quassel IRC is a modern, cross-platform, distributed IRC client, meaning that one (or multiple) client(s) can attach to and detach from a central core - much like the popular combination of screen and a text-based IRC client such as WeeChat, but graphical.

The port has variants for two different flavours of Quassel:

  • monolithic: Stand-alone version, can be used like any other IRC client.
  • client: Connects to a remote Quassel core.

Both flavours can co-exist alongside each other. By default, only the monolithic one is built.

The core (server) component of Quassel is not included in this port.

I chose not to add a kde variant because, well, I doubt it makes a lot of sense on OS X. Also, the transitive dependency closure of kdelibs4 is enormous.

Attachments (1)

Portfile (2.8 KB) - added by macports@… 12 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Type: enhancementsubmission
Version: 2.1.3

comment:2 in reply to:  description Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to macports@…:

The port has variants for two different flavours of Quassel:

  • monolithic: Stand-alone version, can be used like any other IRC client.
  • client: Connects to a remote Quassel core.

Both flavours can co-exist alongside each other. By default, only the monolithic one is built.

Might it make sense to use subports instead of variants for these?

comment:3 Changed 12 years ago by macports@…

Is there any documentation or examples that you could point me to? Looks like subports are largely undocumented.

comment:4 in reply to:  3 Changed 12 years ago by larryv (Lawrence Velázquez)

Replying to macports@…:

Is there any documentation or examples that you could point me to? Looks like subports are largely undocumented.

They are undocumented. Take a look at these, for starters:

Changed 12 years ago by macports@…

Attachment: Portfile added

comment:5 Changed 12 years ago by macports@…

Here's a new Portfile that makes use of subports (quassel and quassel-client, just like in Debian).

comment:6 Changed 12 years ago by neverpanic (Clemens Lang)

Owner: changed from macports-tickets@… to cal@…
Status: newassigned

Commited in r104054. Do you want me to add you as maintainer? If yes, do you also want to mark the port openmaintainer as described in https://guide.macports.org/#project.update-policies?

comment:7 Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: fixed
Status: assignedclosed

comment:8 in reply to:  6 Changed 12 years ago by macports@…

Replying to cal@…:

Commited in r104054. Do you want me to add you as maintainer? If yes, do you also want to mark the port openmaintainer as described in https://guide.macports.org/#project.update-policies?

Why not, go ahead. :-)

comment:9 Changed 12 years ago by neverpanic (Clemens Lang)

Thank you, r104055.

Note: See TracTickets for help on using tickets.