We need to collate, and create when necessary, test benches for each package. The goal is to provide arch testers and users with a way
of checking that an application is properly working.
These test benches can be anything from a set of written instructions to an automated script. They should be as simple as possible.
A non-specialist must be able to use them.
Let's not forget they must be maintained to work with the new versions of the packages.
Stabilize latest versions whenever possible, and get rid of the others. Portage should be kept as lean as possible.
- Stabilize version 8.11.
- See if building versions 8 and later from sources is a good idea (it's java). Current decision is no, but that may change.
- Complete stabilization of version 1.6.1 (see bug #285470).
- Get rid of version 1.4.0-r1 after stabilisation of 1.6.1
- Write a newer ebuild (than version 20050820) with updated dependencies.
- Include gspiceui (see bug #74201)
- Finish stabilization version 2.4.0. (see bug #342811
- Get rid of older versions.
Quite some mess to fix, here. Version 20060708 was stabilized due to version 0.34 not playing nice with gcc 4.1
(if I remember correctly). Recently, version 0.35 was released by upstream, but in portage it appears older than
20060708 although it is more recent. Thus, users not masking versions 2006mmdd, as indicated in the ChangeLog, will
not see the new release.
- Later development versions will need to be called 0.35_p2006mmdd in order to avoid this mess again.
Denis should provide and document the ugly script he uses to generate the custom tarballs.
- Change the package name to ngspice. This is confusing for some users.
- Investigate the use boehm-gc. Heavy simulations can make use of better memory management.