Changeset 8e0b0f3


Ignore:
Timestamp:
07/12/2001 07:36:04 PM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
60bbc31
Parents:
eefe751
Message:

Removed package update procedure - needs to be rewritten

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@802 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • HOWTO_EDIT

    reefe751 r8e0b0f3  
    2323
    2424
    25 * Updating a package's version
    26 
    27 Follow these steps in order to change a package (for example when you tested
    28 a newer version and want to include it in the book). Let's assume you're
    29 upgrading to bash-2.05.
    30 
    31 1) Download bash-2.05 to the linuxfromscratch.org server in the
    32 /home/ftp/conglomeration directory. If the file isn't compressed with bzip2,
    33 but with gzip for example, ungzip it, then bzip2 it.
    34 
    35 2) Enter the /home/ftp/cvs directory.
    36 
    37 3) Remove the symlink that points to the previous version of the
    38 package.
    39 
    40 4) You can remove the real file from the /home/ftp/conglomeration
    41 directory only is you are absolutely sure that there are no other books
    42 currently online that use that package version. If you don't remember
    43 which book versions are online right now, check the LFS website.
    44 
    45 5) Make a new symlink by running the following command:
    46 ln -s ../conglomeration/bash-2.05.tar.bz2
    47 
    48 6) Obtain the file size of the new package (run ls -l
    49 /home/ftp/conglomeration/packagename). Divide this number by 1024 and
    50 remember the result.
    51 
    52 7) Enter the /home/ftp directory and create a new lfs-packages tarball.
    53 If today is June 11th, 2001 1:09 PM, run the following:
    54 tar cvfh lfs-packages-cvs-20010611-1309.tar cvs
    55 mv lfs-packages-cvs-20010611-1309.tar cvs
    56 (use the current date and time on the LFS server, not your local time if
    57 it differs)
    58 
    59 The reason for adding the hour and minute is that one may end up
    60 creating more than one tarball a day and it's easier this way to find
    61 out which packages file was being used in case there are a lot of
    62 updates.
    63 
    64 8) Obtain the file size of the newly created tarball by running ls -l,
    65 divide the number by 1024 and remeber the result.
    66 
    67 9) Open the index.xml file.
    68 
    69 10) At the bottom of the file find the ENTITY that belongs to the package.
    70 You'll find it as <!ENTITY package-version "version">. Change the
    71 bash-version entity as follows: <!ENTITY bash-version "2.05">
    72 
    73 11) Edit the <!ENTITY all-version> entity and update the file name to
    74 match the name of the tarball you just created.
    75 
    76 12) Edit the <!ENTITY all-version> entity and update the file name to
    77 match the name of the new tarball you just created.
    78 
    79 13) Open the chapter3/bash.xml file.
    80 
    81 14) Enter the new size that you calculated in step 6.
    82 
    83 15) Open the chapter3/all.xml file.
    84 
    85 16) Update the file size to match the value you calculated in step 8.
    86 
    87 17) Open the chapter3/packages.xml file, scroll to the bottom of the
    88 file and enter the same size as you entered in the previous step. Also
    89 divide this number by 1024 and enter the result as the MB value between
    90 brackets.
    91 
    92 18) Open chapter1/changelog.xml and add the package to the list.
    93 
    94 Please don't use the "du -h" command to obtain the file size. The result
    95 of du is not acurate enough (it doesn't report the actual file size, but
    96 the size of clusters the file is using).
    97 
    98 If you are updating more than one package at the same time, don't
    99 re-create the tarball every time. Just update all the symlinks and
    100 create a new tarball once that includes all your updated packages.
    101 
    10225
    10326* Adding a new package update to Bugzilla
Note: See TracChangeset for help on using the changeset viewer.