Terrence Miller <terrencem <at> sbcglobal.net> writes: > In current scheme you end up running configure once for each missing > package (since it stops on first error). Sometimes > the error message is useful but not always. I understand the problem, but unfortunately maintaining an up-to-date complete list of deps is a lot of work (since those deps are also constantly moving). What we might try to seduce RelEng to is to make configure output all deps it is looking for, but I dont know if that can be easily (automatically) done.
> At least on Ubuntu there is a way to map from the name of a missing file > to the name of the package supplying > that file. Well, there is some kind of reference all the time - if you are not a package maintainer you can look at the source package of your distro. If you are a package maintainer, you can have a look at the source packages of other distros. > A release is built with some fixed set of options. The documentation has > an example for Ubuntu 9.04 but gives no clue > what to do in any other situations. The wiki page is probably the wrong > place for multiple examples Yep, those infos are kept in the source packages of the distro repo. > > Why would you want to do that in the first place? > > A year later so much stuff has changed in the sources - why would you > > want to build such an old version then? > > > A critical bug in an old release has been reported by an important user > and the latest release contains a UI change the user > is unwilling to adopt. All relevant distros kept their source packages/ebuilds in a repository. Have Fun, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
