[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: BSD port plans for the squeeze cycle



Hi,

especially Aurelien and Cyril ;-)

IMHO, we should discuss it here and to -release sent only result.

As announced on dda [RT1], we want to get an impression when releasing
Squeeze is feasible. We have proposed a (quite ambitious) freeze in December
2009, and some developers have noted that their planned changes wouldn't be
possible in this time frame. So, to find out when releasing would work for
most people, it would be great if you could answer the following questions:

Do you have any big changes planned? How much time would they take, and
what consequences are there for the rest of the project?

How many "big" transitions will the upcoming changes cause? When should those
happen? Can we do something to make them easier?


* decide version of kernel and related utilities.
  It mainly depends on freeze time. Currently we use 7.2. The 8.0 should
  appear soon, but dot-zero is dot-zero ;-) May be 7.3 would be released
  before freeze.

* get rid of libfreebsd
  It waits for eglibc 2.10 upload, only 2 or 3 packages which b-d on
  libfreebsd-dev are not maintained by kfreebsd porters. Some binNMUs
  will be also needed.

* gnat availability on kfreebsd-amd64
  gnat have been recently ported/bootstrapped on kfreebsd-amd64,
  this fact should propagate into debian/control files of ada related
  source packages.

* ghc6 availability on kfreebsd-amd64
  ghc6 is not yet available on kfreebsd-amd64, it have to be
  ported/bootstrapped. The 6.10 series does not support bootstrapping
  at all, the 6.12 should be much better, it should also eliminate
  the need of MAP_32BIT flag of mmap(), which is not available under
  FreeBSD kernel. When ghc6 6.12 become available, there will be need
  to change debian/control files of ghc6 related source packages.

* FTBFS on GNU/kFreeBSD with patches in BTS

* entries in Packages-arch-specific

* port of Debian Installer for GNU/kFreeBSD


What else ?

		Petr


Reply to: