Re: Bug#70269: automatic build fails for potato
>>"Steve" == Steve Greenland <firstname.lastname@example.org> writes:
Steve> Are you saying that someone running a build daemon is not
Steve> going to keep up-to-date on build-essential packages? Why not?
Steve> And if not, why is my (the maintainer's) job to keep changing
Steve> the version numbers in my control file to force it to happen?
Firstly, build essential package is ot merrely for
build daemaons. Therefore packages would need to specify the oldest
version of the build package they can be built with (in the worst
case, exactly the version they were built with), since not every
machine they can be built on can be depended to ahve the altest
version of the helper packages.
Indeed, none of may machines have _any_ helper packages
I think that since every package using a helper package seems
to need a versioned dependency, addign debhelper to build essential
shall not remove the burden from the packages. And auto build daemons
can also augment the build environment beyond build essential, as
they already do.
Am I missing the mark here?
Just go ahead and write your own multitasking multiuser os! Worked
for me all the times. Linus Torvalds
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C