ScarletDME - User contributions [en]

Subversion Repository: HOWTO

2008-12-02T16:52:22Z

WikiSysop: /* Committing Binary Files like VOC/ERRMSG */

== Introduction ==

=== Terminology ===

#Checkout - downloads a copy for the first time
#'''Update''' - downloads your copy with any changes in the repository
#'''Commit''' - uploads any changes you made in your copy to the repository
#Import - upload - can be replaced by a combination of update/commit

repo - repository

depo - your copy

=== Windows Walkthrough ===

http://tortoisesvn.tigris.org/

This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.

The interesting bits of source code management jump out at you later when two people work on the same file at the same time.

*You commit a file which has also committed by someone else AFTER you checked it out
*You update your depo from repo and someone has committed changes to a file that you have already locally changed.

In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.

=== Other tools===

Visual Studio - http://ankhsvn.open.collab.net/

Eclipse - http://subclipse.tigris.org/

Netbeans supports it natively now too. <Diccon> Bean a life saver. (Can we have a few hints, Diccon?)

== HELLO SUBVERSION in Windows==

=== Installation ===

http://tortoisesvn.net/downloads

Might need a reboot

=== Checking Out ===

Right click on your desktop and choose SVN CHECKOUT

Fill in the details

URL? https://gpl.openqm.com/svn/qmvdb

Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT

Click OK

Do you want to create the directory? Yes

Do you want to accept the unsigned certificate? Yes

Wait while it downloads the whole repository

Finished: OK

After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo

Subversion puts a hidden folder called .svn in any folder it is managing

===Acquiring rights to commit===

To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com with the following command where xxxxxxx is the username

htpasswd /etc/subversion/passwd xxxxxxxxx

=== Committing ===

#Open the folder TESTIT
#Create a file called testing.txt anywhere in the folder structure
#Close the folder and notice that it has a big red ! on it showing that something is commitable
#Right click on the TESTIT folder (or indeed any subfolder)
#Choose SVN Commit
#It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All
#It helps to add a message explaining why you are committing
#Click OK
#Enter your committers username and password
#Screen showing upload progress
#Click OK when finished and note that the red ! has changed back into a green tick

== Committing Binary Files like VOC/ERRMSG ==

To subversion, VOC/ERRMSG (and other files? which?) are deemed to be "binary" rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.

The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.

The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.

PRACTICAL SOLUTION FOR NOW

Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.

#SVN UPDATE
#Edit the file
#SVN COMMIT

If you do not do the above then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files

Subversion Repository: HOWTO

2008-12-02T16:49:25Z

WikiSysop: /* Committing Binary Files like VOC/ERRMSG */

== Introduction ==

=== Terminology ===

#Checkout - downloads a copy for the first time
#'''Update''' - downloads your copy with any changes in the repository
#'''Commit''' - uploads any changes you made in your copy to the repository
#Import - upload - can be replaced by a combination of update/commit

repo - repository

depo - your copy

=== Windows Walkthrough ===

http://tortoisesvn.tigris.org/

This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.

The interesting bits of source code management jump out at you later when two people work on the same file at the same time.

*You commit a file which has also committed by someone else AFTER you checked it out
*You update your depo from repo and someone has committed changes to a file that you have already locally changed.

In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.

=== Other tools===

Visual Studio - http://ankhsvn.open.collab.net/

Eclipse - http://subclipse.tigris.org/

Netbeans supports it natively now too. <Diccon> Bean a life saver. (Can we have a few hints, Diccon?)

== HELLO SUBVERSION in Windows==

=== Installation ===

http://tortoisesvn.net/downloads

Might need a reboot

=== Checking Out ===

Right click on your desktop and choose SVN CHECKOUT

Fill in the details

URL? https://gpl.openqm.com/svn/qmvdb

Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT

Click OK

Do you want to create the directory? Yes

Do you want to accept the unsigned certificate? Yes

Wait while it downloads the whole repository

Finished: OK

After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo

Subversion puts a hidden folder called .svn in any folder it is managing

===Acquiring rights to commit===

To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com with the following command where xxxxxxx is the username

htpasswd /etc/subversion/passwd xxxxxxxxx

=== Committing ===

#Open the folder TESTIT
#Create a file called testing.txt anywhere in the folder structure
#Close the folder and notice that it has a big red ! on it showing that something is commitable
#Right click on the TESTIT folder (or indeed any subfolder)
#Choose SVN Commit
#It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All
#It helps to add a message explaining why you are committing
#Click OK
#Enter your committers username and password
#Screen showing upload progress
#Click OK when finished and note that the red ! has changed back into a green tick

== Committing Binary Files like VOC/ERRMSG ==

To subversion, VOC/ERRMSG (and other files? which?) are deemed to be "binary" rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.

The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.

The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.

PRACTICAL SOLUTION FOR NOW

Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.

#SVN UPDATE
#Edit the file
#SVN COMMIT

If you do not do the above then when you finally come to UPDATE or COMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files

Subversion Repository: HOWTO

2008-12-02T16:44:46Z

WikiSysop:

== Introduction ==

=== Terminology ===

#Checkout - downloads a copy for the first time
#'''Update''' - downloads your copy with any changes in the repository
#'''Commit''' - uploads any changes you made in your copy to the repository
#Import - upload - can be replaced by a combination of update/commit

repo - repository

depo - your copy

=== Windows Walkthrough ===

http://tortoisesvn.tigris.org/

This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.

The interesting bits of source code management jump out at you later when two people work on the same file at the same time.

*You commit a file which has also committed by someone else AFTER you checked it out
*You update your depo from repo and someone has committed changes to a file that you have already locally changed.

In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.

=== Other tools===

Visual Studio - http://ankhsvn.open.collab.net/

Eclipse - http://subclipse.tigris.org/

Netbeans supports it natively now too. <Diccon> Bean a life saver. (Can we have a few hints, Diccon?)

== HELLO SUBVERSION in Windows==

=== Installation ===

http://tortoisesvn.net/downloads

Might need a reboot

=== Checking Out ===

Right click on your desktop and choose SVN CHECKOUT

Fill in the details

URL? https://gpl.openqm.com/svn/qmvdb

Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT

Click OK

Do you want to create the directory? Yes

Do you want to accept the unsigned certificate? Yes

Wait while it downloads the whole repository

Finished: OK

After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo

Subversion puts a hidden folder called .svn in any folder it is managing

===Acquiring rights to commit===

To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com with the following command where xxxxxxx is the username

htpasswd /etc/subversion/passwd xxxxxxxxx

=== Committing ===

#Open the folder TESTIT
#Create a file called testing.txt anywhere in the folder structure
#Close the folder and notice that it has a big red ! on it showing that something is commitable
#Right click on the TESTIT folder (or indeed any subfolder)
#Choose SVN Commit
#It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All
#It helps to add a message explaining why you are committing
#Click OK
#Enter your committers username and password
#Screen showing upload progress
#Click OK when finished and note that the red ! has changed back into a green tick

== Committing Binary Files like VOC/ERRMSG ==

To subversion VOC/ERRMSG (and other files? which?) are deemed to be "binary" rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.

The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.

The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.

PRACTICAL SOLUTION FOR NOW

Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.

#SVN UPDATE
#Edit the file
#SVN COMMIT

If you do not do the above then when you finally come to UPDATE or COMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files

Subversion Repository: HOWTO

2008-12-02T16:23:34Z

WikiSysop: /* Committing */

== HELLO SUBVERSION in Windows==

http://tortoisesvn.tigris.org/

This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.

The interesting bits of source code management jump out at you later when two people work on the same file at the same time.

*You commit a file which has also committed by someone else AFTER you checked it out
*You update your depo from repo and someone has committed changes to a file that you have already locally changed.

In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.

=== Other tools===

Visual Studio - http://ankhsvn.open.collab.net/

Eclipse - http://subclipse.tigris.org/

Netbeans supports it natively now too. <Diccon> Bean a life saver. (Can we have a few hints, Diccon?)

=== Installation ===

http://tortoisesvn.net/downloads

Might need a reboot

=== Checking Out ===

Right click on your desktop and choose SVN CHECKOUT

Fill in the details

URL? https://gpl.openqm.com/svn/qmvdb

Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT

Click OK

Do you want to create the directory? Yes

Do you want to accept the unsigned certificate? Yes

Wait while it downloads the whole repository

Finished: OK

After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo

Subversion puts a hidden folder called .svn in any folder it is managing

===Acquiring rights to commit===

To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com with the following command where xxxxxxx is the username

htpasswd /etc/subversion/passwd xxxxxxxxx

=== Committing ===

#Open the folder TESTIT
#Create a file called testing.txt anywhere in the folder structure
#Close the folder and notice that it has a big red ! on it showing that something is commitable
#Right click on the TESTIT folder (or indeed any subfolder)
#Choose SVN Commit
#It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All
#It helps to add a message explaining why you are committing
#Click OK
#Enter your committers username and password
#Screen showing upload progress
#Click OK when finished and note that the red ! has changed back into a green tick

== Committing Binary Files like VOC/ERRMSG ==

To subversion VOC/ERRMSG (and other files? which?) are deemed to be "binary" rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.

The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.

The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.

PRACTICAL SOLUTION FOR NOW

Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.

#SVN UPDATE
#Edit the file
#SVN COMMIT

If you do not do the above then when you finally come to UPDATE or COMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files

Main Page

2008-12-01T16:28:50Z

WikiSysop: /* Services */

== GPL.OPENQM.COM ==

This site is dedicated to the development of the GPL version of openqm by providing a traditional open source environment where anyone can acquire or provide up to the minute bug fixes and developments.

This is a purely GPL project but individual committers are obviously entitled to also submit their work in parallel to Ladybridge, perhaps using diffs, under licences which allow incorporation into Ladybridge's non-GPL codebase. This will minimise the fork and perhaps facilitate further GPL releases from Ladybridge.

The subdomain name is granted by Ladybridge but this server is not their responsibility or under their control.

The gpl.openqm.com server is a vmware 2 virtual machine located in a high bandwidth data centre in Amsterdam, Netherlands. It is hosted by steve.bush@neosys.com who is responsible for daily backup to another data centre in Amsterdam. If you can provide stable high bandwidth backup or VMware 2.0 hosting to mirror outside Europe please contact him.

You must register and login to edit this wiki.

== How do I use this site? ==
If you have a question on how to use the GPl version of OpenQM, then send it to the support and discussion mailing list.

If you want to discuss development of an issue (eg. PHP5 module), and there is no page here for it, then login, and add a page for it. Others will add their contributions to that page.

There is no general discussion forum, because you are expected to edit this site through the wiki links. Feel free to change ANYTHING. If we don't agree with what you do, we can change things back.

There is a developers email list, but really we want you to edit this wiki site directly. That way things don't get lost in the historic trail of emails, and then get asked again.

=== Services ===

*IRC: irc://irc.efnet.org/openqm
*Support and discussion Mailing list (google group): http://groups.google.co.uk/group/openqm-opensource (mailto:openqm-opensource@googlegroups.com)
*Development Mailing list: Register/login: http://gpl.openqm.com/mailman/listinfo/openqm-dev (mailto:openqm-dev@gpl.openqm.com)
*Reporting and tracking bugs: http://gpl.openqm.com/bugzilla
*Wiki: http://gpl.openqm.com/wiki/ (This page)
*Subversion repository: http://gpl.openqm.com/svn/qmvdb/ (currently gives a http 403 forbidden error) - [[HOWTO]]
*[[Downloads]]: automated daily build for key platforms is top priority
*[[Wish list]] - Things that you want & that we need contributors/devs for (lots of small things)

=== Resources ===
*[[QM Client API]] - Documentation and Available API's for the QM remote protocol.
*Billabong Services' Anji - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. [http://billabong-services.co.uk/anji]
*Brian Speir's Installation instructions and other downloads [http://www.rushflat.co.nz/downloads.shtml]
*Kevin Powick's Trident Delphi wrapper [http://www.tridentinfosys.com/]
*Tom Delombard's old QM page. Includes details of the tape utilities and the PHP4 module [http://openqm.blackflute.com/]

--[[Administration]]

Main Page

2008-12-01T16:28:12Z

WikiSysop: /* Services */

== GPL.OPENQM.COM ==

This site is dedicated to the development of the GPL version of openqm by providing a traditional open source environment where anyone can acquire or provide up to the minute bug fixes and developments.

This is a purely GPL project but individual committers are obviously entitled to also submit their work in parallel to Ladybridge, perhaps using diffs, under licences which allow incorporation into Ladybridge's non-GPL codebase. This will minimise the fork and perhaps facilitate further GPL releases from Ladybridge.

The subdomain name is granted by Ladybridge but this server is not their responsibility or under their control.

The gpl.openqm.com server is a vmware 2 virtual machine located in a high bandwidth data centre in Amsterdam, Netherlands. It is hosted by steve.bush@neosys.com who is responsible for daily backup to another data centre in Amsterdam. If you can provide stable high bandwidth backup or VMware 2.0 hosting to mirror outside Europe please contact him.

You must register and login to edit this wiki.

== How do I use this site? ==
If you have a question on how to use the GPl version of OpenQM, then send it to the support and discussion mailing list.

If you want to discuss development of an issue (eg. PHP5 module), and there is no page here for it, then login, and add a page for it. Others will add their contributions to that page.

There is no general discussion forum, because you are expected to edit this site through the wiki links. Feel free to change ANYTHING. If we don't agree with what you do, we can change things back.

There is a developers email list, but really we want you to edit this wiki site directly. That way things don't get lost in the historic trail of emails, and then get asked again.

=== Services ===

*IRC: irc://irc.efnet.org/openqm
*Support and discussion Mailing list (google group): http://groups.google.co.uk/group/openqm-opensource (mailto:openqm-opensource@googlegroups.com)
*Development Mailing list: Register/login: http://gpl.openqm.com/mailman/listinfo/openqm-dev (mailto:openqm-dev@gpl.openqm.com)
*Reporting and tracking bugs: gpl.openqm.com/bugzilla
*Wiki: http://gpl.openqm.com/wiki/ (This page)
*Subversion repository: http://gpl.openqm.com/svn/qmvdb/ (currently gives a http 403 forbidden error) - [[HOWTO]]
*[[Downloads]]: automated daily build for key platforms is top priority
*[[Wish list]] - Things that you want & that we need contributors/devs for (lots of small things)

=== Resources ===
*[[QM Client API]] - Documentation and Available API's for the QM remote protocol.
*Billabong Services' Anji - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. [http://billabong-services.co.uk/anji]
*Brian Speir's Installation instructions and other downloads [http://www.rushflat.co.nz/downloads.shtml]
*Kevin Powick's Trident Delphi wrapper [http://www.tridentinfosys.com/]
*Tom Delombard's old QM page. Includes details of the tape utilities and the PHP4 module [http://openqm.blackflute.com/]

--[[Administration]]

Wish list

2008-12-01T14:55:20Z

WikiSysop:

Things we need or want.

If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.

To keep in touch with this slowly evolving agenda register, making sure you check "email alerts on pages I watch", login and click the "watch" tab at the top of this page.

==Development==
*Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)
*Lastest version DEB package
*QM API list compression
*Revelation binary computability
*QPROC system call
*Svn Linux howto
*[[Logo]]

==Sysadmin==
*Sort /var/www or Apache so we dont have to multi sym link to get dirs visible.
*ftp access? (not sure if we need this)
*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.

==Bugfixes==
*ERRMSG to hold more than one error

Wish list

2008-12-01T14:54:34Z

WikiSysop:

Things we need or want.

If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.

To keep in touch with this slowly evolving agenda making sure you check "email alerts on pages I watch" and click the "watch" tab at the top of this page.

==Development==
*Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)
*Lastest version DEB package
*QM API list compression
*Revelation binary computability
*QPROC system call
*Svn Linux howto
*[[Logo]]

==Sysadmin==
*Sort /var/www or Apache so we dont have to multi sym link to get dirs visible.
*ftp access? (not sure if we need this)
*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.

==Bugfixes==
*ERRMSG to hold more than one error

Main Page

2008-11-28T22:11:37Z

WikiSysop: /* GPL.OPENQM.COM */

Main Page

2008-11-28T17:38:46Z

WikiSysop: /* GPL.OPENQM.COM */

== GPL.OPENQM.COM ==

This site is dedicated to the development of GPL version of openqm. The objective is to provide a traditional open source environment where anyone can acquire or provide up to the minute bug fixes and developments.

While this is a purely GPL project, individual committers are obviously entitled to also submit their work in parallel to Ladybridge, perhaps using diffs, under licences which allow incorporation into Ladybridge's non-GPL codebase. This will minimise the fork and perhaps facilitate further GPL releases from Ladybridge.

The subdomain name is granted by Ladybridge but the server is not their responsibility or under their control.

The gpl.openqm.com server is a vmware 2 virtual machine located in a high bandwidth data centre in Amsterdam, Netherlands. It is hosted by steve.bush@neosys.com who is responsible for daily backup to another data centre in Amsterdam. If you can provide stable high bandwidth backup or VMware 2.0 hosting to mirror outside Europe please contact him.

You must register and login to edit this wiki.

=== Services ===

wiki: http://gpl.openqm.com/wiki/

irc: irc://irc.efnet.org/openqm

repository: subversion coming

dev email list: http://gpl.openqm.com/mailman/listinfo/openqm-dev

support email list: mailto:openqm-opensource@googlegroups.com http://groups.google.co.uk/group/openqm-opensource

downloads:

future: download automated builds derived from the repository

=== Administration ===

http://gpl.openqm.com/mailman/admin/openqm-dev

https://gpl.openqm.com:14920/