Re: Making a srouce package Bug - #859130 ITP: lina -- iso- Forth interpreter
>I'm not ready to tackle systemd yet. :-( .
I don't care about you running an up-to-date systems, but be careful
because uploading and building is done on "unstable", not "oldstable",
so prepare chroots, pbuider/sbuild or whatever that will make you
use the correct toolchain, to avoid build failures or whatever bug
due to this
>That is as "upstream" as can be so yes, you are right to stop there.
>The only thing that could be of interest to Debian are upstream source
>distributions in the directory release. I shouldn't have called it
>a package.
ack :)
>That is .s as in assembler. This package has been written in assembler.
>I understand that you find that hard to believe.
I like assembler, and I don't find it hard to believe
>Every instruction has been handcrafted, not compiled.>This is for one architecture of course.
ack
>The package has no runtime dependancies, only build time. No static
>libraries,
>no dynamic libraries.
>
>Tell me how to proceed to make a proper Debian source package from it
>or tell me that such a package can never be turned into a proper Debian
>package.
write a makefile, put the list of architectures that the package should
build in control file
and so on.
"dh_make" should be handy for starting with a debian skeleton
we want everything built from the "preferred source of modification".
So, if you develop your tool by changing assembly code this is completely
fine.
G.
Reply to: