Differences between revisions 36 and 37
Revision 36 as of 2007-01-18 09:59:00
Size: 7902
Comment: Some verbosity added.
Revision 37 as of 2007-01-18 12:11:40
Size: 8146
Comment: anonymous ssh access added
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
}}}
This creates a folder "pkg-boinc" in your current working directory. In there, the folder 'trunk' has all data that is required to mold the upstream code into a Debian package. This is explained along the tool 'svn-buildpackage' further below.
}}}If you do not have an Alioth account, then alternatively choose the anonymous access {{{
svn co svn://svn.debian.org/pkg-boinc
}}} However, for the latter case it is not possible to submit data back to the subversion repository.

The svn checkout creates a folder "pkg-boinc" in your current working directory. In there, the folder 'trunk' has all data that is required to mold the upstream code into a Debian package. This is explained along the tool 'svn-buildpackage' further below.

The purpose of this page is to provide resources to aid members of the Debian ["BOINC"] maintenance team in packaging ["BOINC"] and related software.

Using the Subversion repository

Development is coordinated through a [http://svn.debian.org/wsvn/pkg-boinc Subversion repository]. It follows a brief HOWTO for working with this repository. There is also a ["SmallSVNTutorial"] on this wiki. For a detailed introduction in Subversion have a look at the [http://svnbook.red-bean.com/ Version Control with Subversion] book.

  • Download the files from the the repository. Substitute smoe-guest in the URL with your userid on Alioth:

svn co svn+ssh://smoe-guest@svn.debian.org/svn/pkg-boinc

If you do not have an Alioth account, then alternatively choose the anonymous access

svn co svn://svn.debian.org/pkg-boinc

However, for the latter case it is not possible to submit data back to the subversion repository.

The svn checkout creates a folder "pkg-boinc" in your current working directory. In there, the folder 'trunk' has all data that is required to mold the upstream code into a Debian package. This is explained along the tool 'svn-buildpackage' further below.

  • Now, files can be edited and subsequently be submitted (checked in) back to the repository:

svn commit
  • To get the latest version again, run update without the reqirement of specifying the URL again. The URL (and other details) are stored locally

in the files of the hidden '.svn' directory:

svn update

../../scripts/export-boinc -r 4.72

to get the tagged version from the upstream CVS repository. This will perpare the upstream source in a tar ball. It gets a version number as part of its file name and the characteristic ".orig" tag, thus rendering the tar directly usable as input for the dpkg-buildpackage script.

Once you obtained a source tarball run

svn-buildpackage -rfakeroot -uc -us --svn-ignore

in the directory trunk/boinc/ and subsequently inspect the file trunk/boinc/.svn/deb-layout. That file defines origDir, the directory where the .orig.tar.gz files are stored. Adjust this variable and/or move source to the default location, e.g. by a

mkdir tarfiles && mv boinc*orig.tar.gz tarfiles

. With the adjusted setting, another run of svn-buildpackage -rfakeroot should build BOINC source and binary packages.

  • Some instruction of the internet suggested to create the following aliases in one's .bashrc file:

alias svn-b='svn-buildpackage -us -uc -rfakeroot --svn-ignore'
alias svn-br='svn-b --svn-dont-purge --svn-reuse --svn-ignore'
alias svn-bt='svn-buildpackage --svn-tag -rfakeroot'

The ' --svn-ignore' option avoids that for every call to 'svn-buidpackage' on has to submit the changes to the server. In our view one should decide for oneself and in communication with the other developers for the moment to submit changes. One should not forget about it, though!

For remaining questions send an email to our [http://lists.alioth.debian.org/mailman/listinfo/pkg-boinc-devel mailing list].

?Anchor(TODO)

To-do list

  • Things that need to be done before uploading to DebianUnstable:

    • none

  • Things that need to be done before releasing the next upstream release:
    • none

  • General major TODOs:
  • General minor TODOs:
  • Thoughts for the Wiki:
    • Explain how to set up a project
    • Create more sub pages for
      • Trouble shooting

Bookmarks for BOINC in Debian

Packages for other operating systems