[fink-core] Re: 0.7.1 Announcement Draft scheduled for Monday 9am GMT+1

[<mic...@ea...>]

Le 19 sept. 2004, =E0 18:13, Martin Costabel a =E9crit :

> Mich=E8le Garoche wrote:
>
>> This is a bit out of topic, but what happens to the layout of  =20
>> compare.php, it is unusable/unreadable as is. All packages listed in  =
=20
>> Indian file, without any break per package/maintainer... I doubt =20
>> anyone  would make the effort to read it.
>
> I made a small change to compare.php which should fix this (there were =
=20
> </li> tags without <li>). This red/green/white stuff seems broken. I =20=

> always see
>
> Total: green, red, white packages.
>
> But I don't remember what these were for, anyway. I guess it doesn't =20=

> matter.
Yes, it matters. This is here to allow maintainers to tell this package =20=

does not compile, should never go to stable, or is already (or ok to =20
go) in stable.

At that time, there was a table with all packages and a column to =20
change the status, test it with this:

http://fink.sourceforge.net/pdb/compare.php?tree1=3Dcurrent-10.2-gcc3.3-=20=

unstable&cmp=3D0&tree2=3Dcurrent-10.3-unstable&sort=3Dmaintainer

It's very important to have a correct layout here also, normally the =20
checkbox should be on the same line as the maintainer's name, the =20
package's name and the version.

As there are a bunch of packages, it is convenient to be able to hide =20=

packages which don't compile or should not be moved, so that you only =20=

view the packages which need to be tested (ok or not to go in stable). =20=

This is done checking the white, green, or red checkbox. It it used =20
when there a massive passage from one tree to another (i.e. 10.2-gcc3.3 =20=

to 10.3). It is likely that it will be used in the future.

Mich=E8le
<http://micmacfr.homeunix.org>