Author: benm
Date: 2005-05-04 19:12:59 -0400 (Wed, 04 May 2005)
New Revision: 44055
Removed:
trunk/release/build-notes
trunk/release/deploy-howto
trunk/release/packaging-howto
Log:
remove completely outdated info
Deleted: trunk/release/build-notes
===================================================================
--- trunk/release/build-notes 2005-05-04 23:07:48 UTC (rev 44054)
+++ trunk/release/build-notes 2005-05-04 23:12:59 UTC (rev 44055)
@@ -1,62 +0,0 @@
- How to do a Mono release
-==========================
-
-1) Checkout 'mcs' and 'mono' to /tmp
-
-2) Build mcs
-
-3) Build mono, with 'make distcheck'
-
-4) Commit fixes from distcheck; if needed, go to 1
-
-5) Check out a pristine mcs tree again
-
- * Rename to mcs-RELEASE
-
- * Tar it up (excluding CVS dir)
-
-
- How to upload packages to RC
-==============================
-
-1) ssh into [EMAIL PROTECTED]
-
-2) Upload new packages to /nfs/user/duncan
-
-3) rel-add-packages -s -c mono -t [target] -d "mono release" [path to files]
-
-4) rel-stage-to-real mono
-
-5) rel-push
-
-**** DO NOT PUSH SOURCE RPMS!!! ****
-
-
-How to use the build system
-============================
-
-1) Upload tarball to /nfs
-
-2) bb_submit the tarball
-
-3) Optionally, edit the conf file to bump version count, etc.
-
-4) bb_redo or bb_client
-
-[[prefix]] -- prefix on distro
-
-bb_unpack -c -- cleans the tree
-
-bb_redo == bb_unpack -c; bb_unpack; bb_do (builds)
-
-export BB_REPODIR=/nfs/release/source_repository/
-
-
-How to create a StrongName key pair
-====================================
-
-[20:38] <spouliot> creating a strongname key pair is easy
-[20:38] <spouliot> sn -k keypair.snk
-[20:38] <spouliot> then extract the public key
-[20:38] <spouliot> sn -p keypair.snk keypair.pub
-
Deleted: trunk/release/deploy-howto
===================================================================
--- trunk/release/deploy-howto 2005-05-04 23:07:48 UTC (rev 44054)
+++ trunk/release/deploy-howto 2005-05-04 23:12:59 UTC (rev 44055)
@@ -1,74 +0,0 @@
-How to upload the packages
-==========================
-
-Part A: Uploading to the web site
-
-1) Connect to [EMAIL PROTECTED]
-
-2) There's a script called make-directories to create the new
- skeleton.
-
- To based a 1.x release from the 1.0 tarball, run the follow from
- the "archive" directory.
-
- make-directories 1.0 1.x
-
- This assumes that "1.0" and "1.x" are both a child directory of
- "archive".
-
-3) Copy everything to the 1.x directory from the NFS deploy directory:
-
- scp -R /nfs/$USER/deploy/1.x/ [EMAIL PROTECTED]:go-mono/archive/1.x/
-
- This copies all the new files into 1.x, with all new the RPMS
- landing in the correct subdirectory containing the packages from the
- previous release.
-
-4) For each of the subdirectories containing the packages for each
- distribution, remove those that will be replaced by the new
- packages. There should be a script for doing this, but it hasn't
- been written yet.
-
-5) Inspect the subdirectories again, making sure everything is in
- place. Check to make sure the serial numbers are the consistent
- (i.e. you didn't copy packages for the FOO distribution to the BAR
- directory)
-
- For Fedora packages, run "yum-arch -l ." from the subdirectory with
- all the RPMs to generate the headers directory and other
- YUM-related stuff. The "-l" flag is necessary for having YUM use
- the symbolic links (those from make-directories).
-
-6) Run "update-all" from the "1.x" directory. It's call "update-zip"
- to create the "mono-all.zip" files, and call "update-page" to
- generate the index page for each distribution. Be sure to update
- "template.html" to reflect the updated version number.
-
-7) Go to "archive/yum-repository" and update the symbolic links
- to point to the latest Fedora release directory.
-
-
-Part B: Uploading to Red Carpet
-
-1) You'll need access to connect to "[EMAIL PROTECTED]".
-
-2) Go to the deployment directory on NFS.
-
-3) Assuming that the directory is laid out as described, run:
-
-<shell-script>
- for i in *; do
- rel-add-packages -c mono -t $i -d "A Brief message here" $i/*.rpm;
- done
-</shell-script>
-
- Where $i is the target, or the name of the distribution.
-
- We currently support the following distributions:
-
- redhat-9-i386, fedora-1-i386, fedora-2-i386, suse-90-i586,
- suse-91-i586, sles-8-i386
-
-4) Once that is completed, call "rel-stage-to-real mono"
-
-5) After that, "rel-push".
\ No newline at end of file
Deleted: trunk/release/packaging-howto
===================================================================
--- trunk/release/packaging-howto 2005-05-04 23:07:48 UTC (rev 44054)
+++ trunk/release/packaging-howto 2005-05-04 23:12:59 UTC (rev 44055)
@@ -1,71 +0,0 @@
-How to build RPM packages for a release
-=======================================
-
-Part A: Submit the tarballs and update the conf file
-
-1) Log into hardhat as builder.
-
-2) Download all the release tarballs for that release, and for each
- tarball, run "bb_submit $tarball" to add to the source
- repository. The submission process will return the full name of the
- tarball. For example, submitting "foo.tar.gz" for the first time
- will lead to "foo.tar.gz-1". If you submit another time, it will be
- "foo.tar.gz-2".
-
-3) Update the <version> element in each of the ximian-build.conf files
- in conf/mono-conf/$module to reflect the full name of the latest
- tarball.
-
-
-Part B: Connect to the jails
-
-1) When you log in to [EMAIL PROTECTED], it'll print out a listing of the
- available jails.
-
-2) For each of the distribution, connect to the appropriate jail (the
- command is listed)
-
-
-Part C: Build packages
-
-1) Run "sh clear-packages" to clean up the output dir.
-
-2) For each module, "cd conf/mono-conf/$module" and run "bb_redo". Make
- sure that it's building from the newly updated tarball, and not the
- old one.
-
-3) Copy the resulting RPMs (in /tmp/$user/built-packages) to a
- directory on NFS for deployment. In general, I put them in
- "/nfs/$USER/deploy/$RELEASE/$DISTRIBUTION/" in my NFS
- dir. $DISTRIBUTION should be the same as the name used by RC, this
- makes uploading the files much easier.
-
- Remember: DO NOT COPY SOURCE RPMS AND DEBUGINFO RPMS.
-
-4) If the package doesn't build, write a patch to fix the problem.
-
-
-Part D: How to make a patch
-
-1) For each module, there will be a "src" directory with the pristine
- source code and a "BUILD" directory for running the build. Using
- the "BUILD" directory, figure out what changes need to be made. If
- these directories are not available, run "bb_unpack".
-
-2) Apply the changes to the "src" directory.
-
-3) With the changes made, go back to the root module directory (parent
- of src and BUILD), and call "bb_regenerate <name of patch>".
-
-4) A "foo.patch.new" will be created, read it and make sure it
- contains the valid changes. Rename it to "foo.patch". Submit the
- patch to the repository ("bb_submit foo.patch").
-
-5) In the ximian-build.conf file, parallel to the <source> element,
- put in a new <patch> element like this:
-
- <patch>
- <i>foo.patch-1</i>
- </patch>
-
-6) Run "bb_redo" again, make sure the patch is applied.
_______________________________________________
Mono-patches maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-patches
