The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: archive maintainance

From: Craig Sanders <cas@taz.net.au>
> What happens when the source for package-i386.deb is different from
> package-alpha.deb?

Let's please _not_ do that.

> yes, i know that other architecture patches _should_ be merged back into
> one source file with conditional defines but that isn't always going to
> happen straight away...especially if the i386 maintainer and the alpha
> maintainer live thousands of miles apart and can communicate only by a
> slow and flaky connection.

Let's please have them work together. If they work together on platforms
1 and 2, platform 3 is going to be a lot easier. Since we have simultaneous
ports going on, it becomes essential that one person merge all changes into
the source. Since the changes for platform 2 are often the same changes
necessary for platform 3, I tend to prefer the #ifdef style to
architecture-specific diff files. Having this stuff appear in the source
points out the portability problems in a program.

If the 68k maintainer is making a lot of changes to something that was
i386-only up to now, it's permissible for the main maintainer to "hand
the baton" to the 68k maintainer for some time, so that the 68k maintainer
would upload the source package and both 68k and i386 binaries.

	Thanks

	Bruce