mirror of
https://git.rtems.org/rtems-docs/
synced 2025-05-14 23:09:16 +08:00
RSB: Fix the history.
This commit is contained in:
parent
ce4daf9fd9
commit
3d055ece4e
@ -1,24 +0,0 @@
|
|||||||
.. comment SPDX-License-Identifier: CC-BY-SA-4.0
|
|
||||||
|
|
||||||
.. comment COPYRIGHT (c) 2012 - 2016.
|
|
||||||
.. comment Chris Johns <chrisj@rtems.org>
|
|
||||||
|
|
||||||
History
|
|
||||||
#######
|
|
||||||
|
|
||||||
The RTEMS Source Builder is a stand alone tool based on another tool called the
|
|
||||||
'SpecBuilder'. The SpecBuilder was written for the RTEMS project to give me a
|
|
||||||
way to build tools on hosts that did not support RPMs. At the time the RTEMS
|
|
||||||
tools maintainer only used spec files to create various packages. This meant I
|
|
||||||
had either spec files, RPM files or SRPM files. The RPM and SPRM files where
|
|
||||||
useless because you needed an 'rpm' type tool to extract and manage them. There
|
|
||||||
are versions of 'rpm' for a number of non-RPM hosts however these proved to be
|
|
||||||
in various broken states and randomly maintained. The solution I settled on was
|
|
||||||
to use spec files so I wrote a Python based tool that parsed the spec file
|
|
||||||
format and allowed me to create a shell script I could run to build the
|
|
||||||
package. This approach proved successful and I was able to track the RPM
|
|
||||||
version of the RTEMS tools on a non-RPM host over a number of years. however
|
|
||||||
the SpecBuilder tool did not help me build tools or other packages not related
|
|
||||||
to the RTEMS project where there was no spec file I could use so I needed
|
|
||||||
another tool. Rather than start again I decided to take the parsing code for
|
|
||||||
the spec file format and build a new tool called the RTEMS Source Builder.
|
|
@ -141,16 +141,16 @@ The RTEMS Source Builder is a stand alone tool based on another tool called the
|
|||||||
for the RTEMS project to provide Chris with a way to build tools on hosts that
|
for the RTEMS project to provide Chris with a way to build tools on hosts that
|
||||||
did not support RPMs. At the time the RTEMS tools maintainer only supported
|
did not support RPMs. At the time the RTEMS tools maintainer only supported
|
||||||
*spec* files and these files held all the vital configuration data needed to
|
*spec* files and these files held all the vital configuration data needed to
|
||||||
create suitable tool sets. Available SRPM and *spec* files by themselves where
|
create suitable tool sets. The available SRPM and *spec* files by themselves
|
||||||
useless because a suitable ``rpm`` tool to use them was needed. At the time
|
where of little use because a suitable ``rpm`` tool was needed to use them. At
|
||||||
available versions of ``rpm`` for a number of non-RPM hosts were broken and
|
the time the available versions of ``rpm`` for a number of non-RPM hosts were
|
||||||
randomly maintained. The solution Chris settled on was to use the *spec* files
|
broken and randomly maintained. The solution Chris settled on was to use the
|
||||||
and write to a Python based tool that parsed the *spec* file format creating a
|
*spec* files and to write a Python based tool that parsed the *spec* file
|
||||||
shell script that could be run to build the package. The approach proved
|
format creating a shell script that could be run to build the package. The
|
||||||
successful and Chris was able to track the RPM version of the RTEMS tools on a
|
approach proved successful and Chris was able to track the RPM version of the
|
||||||
non-RPM host for a number of years.
|
RTEMS tools on a non-RPM host for a number of years.
|
||||||
|
|
||||||
The *SpecBuilder* tool did not build tools or packages unrelated to the RTEMS
|
The *SpecBuilder* tool did not build tools or packages unrelated to the RTEMS
|
||||||
project where no suitable *spec* file was available so another tool was
|
Project where no suitable *spec* file was available so another tool was
|
||||||
needed. Rather than start again Chris decided to take the parsing code for the
|
needed. Rather than start again Chris decided to take the parsing code for the
|
||||||
*spec* file format and build a new tool called the RTEMS Source Builder.
|
*spec* file format and build a new tool called the RTEMS Source Builder.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user