-------- Oorspronkelijke bericht -------- Onderwerp: Re: Preliminary questions for sponsoring a compiler Datum: 2016-07-25 16:15 Afzender: Paul Wise <p...@debian.org> Ontvanger: Albert van der Horst <alb...@spenarnc.xs4all.nl> Not sure why you moved the discussion off-list, in Debian we prefer to discuss things in public. Feel free to forward my reply to -mentors. On Mon, 2016-07-25 at 15:58 +0200, Albert van der Horst wrote:
My (upstream) build system is complicated and sophisticated. It generates booting, msdos, windows dpmi, windows 32, OSX, linux compilers in 16 32 and 64 bit from the same source file, together with fitting documentation and tests. Hardly something to throw over the > wall.
Sounds useful to publish to me.
The assembler files are merely intermediate files here.
Then they are not source code, not the preferred form for modification and should not be included in the upstream VCS and tarballs.
lina (for the moment) is limited to x86 architectures (32 and 64) as well. ARM lina is under way, but the nature of lina requires adaptation for each architecture anyway. Do you really mean there are ways to build assembler projects that are agnostic of architecture?
I'm not sure about that, but there are certainly assemblers available that run on multiple architectures. nasm for example.
So my conclusion is that I'll supply a public build system and keep the remainder private.
That sounds very much not anything like open source software to me, please put the entirety of your upstream source code and build system into a public project and VCS.
The GNU c-compiler is prebuilt, in order to compile main. Likewise I can only build lina with lina if I supply a prebuilt lina. So I interpret that as no, the GNU c-compiler has a monopoly to the prebuilt case.
No, the GNU c-compiler source code tarball does not contain a pre-built copy of itself. I guess it does require itself to build though, which is fine but different to containing a built copy of itself.
I understand now that there must be a maintainer and a sponsor. I would gladly be the maintainer of the package, but I thought that makes me one of the debian developers, an elite group with restricted membership? How do I apply? Also I'll need a lot of help.
Perhaps this document will clear things up: http://mentors.debian.net/intro-maintainers As upstream, you may also want to take a look at this: https://wiki.debian.org/UpstreamGuide -- Suffering is the prerogative of the strong, the weak -- perish. Albert van der Horst
signature.asc
Description: PGP signature
