I'm working on it, but it's a bit odd in that we need two tarballs to get the manual as well as the base package.

CC: (none) => zen25000
Assignee: bugsquad => zen25000

I just hit a potential brick wall.

FreeBASIC is written in (yep you guessed) FreeBASIC.

We need to use a pre-compiled binary of FreeBASIC (which is in the tarball) to build it, however we do have the source.

Importing a pre-built binary is against Mageia policy, so unless an exception could be made it's a show-stopper.

We could import intermediate asm files from which to build the freebbasic compiler binary to do the build.

Would that be acceptable?

@marja Could you please cc whoever you think best to make a decision on this - thanks.

(In reply to comment #2)
> I just hit a potential brick wall.
> 
> FreeBASIC is written in (yep you guessed) FreeBASIC.
> 
> We need to use a pre-compiled binary of FreeBASIC (which is in the tarball) to
> build it, however we do have the source.
> 
> Importing a pre-built binary is against Mageia policy, so unless an exception
> could be made it's a show-stopper.
> 
> We could import intermediate asm files from which to build the freebbasic
> compiler binary to do the build.
> 
> Would that be acceptable?
> 
> @marja Could you please cc whoever you think best to make a decision on this -
> thanks.


@ misc

Can you look into this, please? I heard you did a lot of bootstrapping to get Mageia started :)

CC: (none) => misc

Link to project web site:-
http://www.freebasic.net/

Is there any decision about this "pre-built binary" problem?

Seems not.

I did chat with upstream when I was last looking at this package and it seems that this issue is a show stpper for several distros, not just us.

Ok, do we have the same "problem" with GCC? Does this compiler write in C?

Freebasic is now available in Cauldron.

Status: NEW => RESOLVED
CC: (none) => jani.valimaa
Resolution: (none) => FIXED