To create new wiki account, please join us on #znc at Libera.Chat and ask admins to create a wiki account for you. You can say thanks to spambots for this inconvenience.

SVN and Irssi: Difference between pages

From ZNC
(Difference between pages)
Jump to navigation Jump to search
Created page with "__toc__ === What is SVN? === (from [http://en.wikipedia.org/wiki/Subversion_%28software%29 Wikipedia]) '''Subversion''' is an open source application for revision control. Al..."
 
m Reverted edits by MetaNova (talk) to last revision by Johncs
Tag: Rollback
 
Line 1: Line 1:
__toc__
== Connecting to ZNC ==
=== What is SVN? ===
=== SSL ===
(from [http://en.wikipedia.org/wiki/Subversion_%28software%29 Wikipedia])


'''Subversion''' is an open source application for revision control. Also commonly referred to as svn or [[SVN]]. It is used to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly-compatible successor to the widely used Concurrent Versions System (CVS).
/network add freenode
/server add -net freenode -auto -ssl my.bouncer.net 6697 username/freenode:password
/save
/connect freenode


=== Is the ZNC code in SVN the bleeding edge? How stable is it? ===
=== Non SSL ===
It's definitely cutting edge. Bugfixes will show up in SVN very early. New features, however, won't show up in SVN before they have somewhat stabilized. This means that SVN versions usually are very stable, but may still contain unknown bugs. If you'd like to help make ZNC better, you are invited to check out the latest revision from SVN and give it a whirl.


=== How do I get the latest SVN revision? ===
/network add freenode
There basically are two ways. One way is to use the svn client utility from your command line:
  /server add -net freenode -auto my.bouncer.net 6667 username/freenode:password
  svn co https://znc.svn.sourceforge.net/svnroot/znc/trunk znc
/save
Without subversion you can use http://znc.in/nightly/znc-svn-latest.tar.gz to get a tarball of the trunk. A new nightly tarball is generated every night, so if there has been a fresh update to SVN, it will usually take some hours before the nightly has the update as well.
/connect freenode


Alternatively, you can try to get a tarball from Sourceforge: http://znc.svn.sourceforge.net/viewvc/znc/trunk.tar.gz?view=tar
=== Timestamps ===


=== Where do experimental patches etc. go? ===
irssi does not support the server-time capability yet, so buffer playback may look ugly. There's a script you can run to get basic server-time support in irssi however, see [[Timestamps#irssi]].
You can find stuff like that on git (another version control system). You can browse git here: http://git.znc.in/?p=psychon/znc.git;a=summary and here: http://git.znc.in/?p=kroimon/znc.git;a=summary.


=== SVN Repository Structure ===
== Notes ==
'''branches''' on svn.kuja.in: contains the development branches of the users working there, currently it's only crox


'''tags''': empty as of now
Irssi does not send unknown commands to irc server or znc so you will get an unknown command error when you try to use the <code>/znc</code> alias. If you want <code>/znc</code> to work you need to enter <code>/alias znc msg *status</code>.


'''trunk''': the main directory for development is here, though don't use the trunk on svn.kuja.in, it's broken
Or, you can download [http://scripts.irssi.org/scripts/dispatch.pl dispatch.pl] placing the script in <code>~/.irssi/scripts/autorun</code> and typing <code>/script load autorun/dispatch</code>. You will only need to enter the command once as irssi will automatically load the script next time irssi is started.


To see the latest changes in the SVN repository structure check here: http://znc.svn.sourceforge.net/viewvc/znc/
Irssi by default will create new channel windows each time znc reconnects to the irc network. After you join all your channels you can enter <code>/layout save</code> to have irssi reuse channel windows instead of creating new windows.


=== What is the crox repository/branch? ===
[[Category:Clients]]
The [[SVN]] repository on Sourceforge is the primary repository, the code in that repository will definitely find its way into a new release.
 
The [[SVN]] repository on svn.kuja.in has been used for development work that didn't find its way into the Sourceforge one mostly because either the stuff there needs to be tested, isn't considered ready for merging by the developers or is made by non-[[ZNC]] developers and isn't merged into mainline yet.
'''It's very outdated, currently!''' If you want to have a look anyway:
svn co svn://svn.kuja.in/znc/branches/crox znc

Revision as of 23:35, 30 July 2019

Connecting to ZNC

SSL

/network add freenode 
/server add -net freenode -auto -ssl my.bouncer.net 6697 username/freenode:password
/save
/connect freenode

Non SSL

/network add freenode 
/server add -net freenode -auto my.bouncer.net 6667 username/freenode:password
/save
/connect freenode

Timestamps

irssi does not support the server-time capability yet, so buffer playback may look ugly. There's a script you can run to get basic server-time support in irssi however, see Timestamps#irssi.

Notes

Irssi does not send unknown commands to irc server or znc so you will get an unknown command error when you try to use the /znc alias. If you want /znc to work you need to enter /alias znc msg *status.

Or, you can download dispatch.pl placing the script in ~/.irssi/scripts/autorun and typing /script load autorun/dispatch. You will only need to enter the command once as irssi will automatically load the script next time irssi is started.

Irssi by default will create new channel windows each time znc reconnects to the irc network. After you join all your channels you can enter /layout save to have irssi reuse channel windows instead of creating new windows.

Retrieved from "https://wiki.znc.in/index.php?title=SVN&oldid=2580"