[Bug 1196] Getting Started Does not Insert Versions Correctly.

rtems-bugs at rtems.org rtems-bugs at rtems.org
Fri Dec 22 14:00:03 UTC 2006


------- Comment #3 from joel.sherrill at oarcorp.com  2006-12-22 08:00 -------
(In reply to comment #2)
> (In reply to comment #1)
> > I think this is a build issue syncing the documentation with the new RPM
> > scripts.
> Well, though it's correct, the versions do not show up inside of the docs, the
> real causes are elsewhere - This whole stuff is fundamentally broken:
> 1. We don't have one common "toolchain" for all targets, anymore. We now have
> different versions per tool/per target => We don't have "common versions" which
> can be applied.

I realized this as I was looking at the download helper.  It fundamentally
makes that more difficult also.

I think I would be happy if it was possible to just have an ASCII file
with each RPM set which listed each target and the sources used.  Right
now, the information is only in the RPMS.

Can that be generated easily as part of the build procedure?

Assuming that when I cut a release tarball I have the "right" RPMs on the
machine cutting the releases, the script generates a list of the RPMs 
that are recommended for that tarball.  Given that and a list of 
target/source files per RPM, anyone should be able to reproduce it 
by hand.

> 2. The toolchains and the files containing their configuration are outside of
> the RTEMS source-tree. They are spread across subdirs of contrib/crossrpms,
> which is not part of the RTEMS source-tree and not in "setup.def" anymore.


> 3. The fact some "versions" appear to work is a random accident.

I suspected as much.

> => I don't know what to do about this. I think the easiest short term work
> around would be to pick some arbitrary target and hard code its current setup
> into the files emphasizing them to be an example.

But the versions will always be wrong.  Maybe a templated type name and
instructions on how to find the right patch and tarball files.

> In longer terms, this whole section needs to be rewritten.

I'm not opposed to that.  I just don't know how to tell someone where to
go to know the right set of RPMs to look at and how from there to know what 
is in them without them dumping a SRPM. 


Configure bugmail: http://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the bugs mailing list