Commit | Line | Data |
---|---|---|
4dd335d4 JM |
1 | Creating Upstream Tarball |
2 | ------------------------- | |
3 | ||
4 | The upstream maintainers distribute SML/NJ as a collection of | |
5 | tarballs. This source package requires all of them, so the Debian orig | |
6 | tar file contains all the upstream tarballs placed where the upstream | |
7 | install.sh script expects them to be unpacked. | |
8 | ||
9 | For example: | |
10 | ||
11 | smlnj-110.x.orig/ckit.tgz | |
12 | smlnj-110.x.orig/config.tgz | |
13 | smlnj-110.x.orig/src/MLRISC.tgz | |
14 | smlnj-110.x.orig/src/cm.tgz | |
15 | smlnj-110.x.orig/src/cml.tgz | |
16 | smlnj-110.x.orig/src/compiler.tgz | |
17 | smlnj-110.x.orig/src/eXene.tgz | |
18 | smlnj-110.x.orig/src/ml-burg.tgz | |
19 | smlnj-110.x.orig/src/ml-lex.tgz | |
20 | smlnj-110.x.orig/src/ml-nlffi-lib.tgz | |
21 | smlnj-110.x.orig/src/ml-nlffigen.tgz | |
22 | smlnj-110.x.orig/src/ml-yacc.tgz | |
23 | smlnj-110.x.orig/src/runtime.tgz | |
24 | smlnj-110.x.orig/src/smlnj-c.tgz | |
25 | smlnj-110.x.orig/src/smlnj-lib.tgz | |
26 | smlnj-110.x.orig/src/system.tgz | |
27 | smlnj-110.x.orig/src/tools.tgz | |
28 | ||
29 | The upstream boot images, used to create the bootstrap compiler are | |
30 | kept in the bootstrap directory, like this: | |
31 | ||
32 | smlnj-110.x.orig/bootstrap/boot.alpha32-unix.tgz | |
33 | smlnj-110.x.orig/bootstrap/boot.hppa-unix.tgz | |
34 | smlnj-110.x.orig/bootstrap/boot.mipseb-unix.tgz | |
35 | smlnj-110.x.orig/bootstrap/boot.ppc-unix.tgz | |
36 | smlnj-110.x.orig/bootstrap/boot.sparc-unix.tgz | |
37 | smlnj-110.x.orig/bootstrap/boot.x86-unix.tgz | |
38 | ||
39 | Use the mkorig script in this directory to create the upstream tarball | |
40 | as used by Debian. Support for the mkorig script has now been | |
41 | integrated into the debian/watch file. Just calling "uscan" will now | |
42 | automatically build a new tarball, if a new upstream version is | |
43 | available. You will need to manually make the mkorig script executable: | |
44 | ||
45 | $ chmod +x debian/mkorig | |
46 | $ uscan --verbose | |
47 | ||
48 | You can still call mkorig manually, although the syntax is a bit | |
49 | different: | |
50 | ||
51 | $ mkorig --upstream-version 110.53 | |
52 | ||
53 | SML/NJ for amd64 architecture | |
54 | ----------------------------- | |
55 | ||
56 | This version of the smlnj package for the amd64 architecture has i386 | |
57 | binaries in it. As the upstream says it: | |
58 | # As long as we do not natively support the amd64 architecture, | |
59 | # we should fallback to the x86 compatibility mode. --Stef | |
60 | x86_64) ARCH=x86;; | |
61 | ||
62 | Building packages at all for amd64 is arguably broken under these | |
63 | circumstances, but it still seemed like the better option. As long as | |
64 | you're aware of this. | |
65 | ||
66 | -- Daniel Moerner <dmoerner@gmail.com>, Fri, 16 Oct 2009 01:01:37 -0700 |