Turnkey source packages (non x86)

Asked by Frans van Berckel on 2009-10-19

Please post the source packages in code or archive to test build these on non x86 machines. Did you create a building and testing script environment? Because that could be useful to do the job. Have PowerPC and Spac64 running Ubuntu available.

Question information

Language:
English Edit question
Status:
Answered
For:
TurnKey Linux Edit question
Assignee:
No assignee Edit question
Last query:
2009-10-19
Last reply:
2009-11-08

This question was originally filed as bug #455712.

Alon Swartz (alonswartz) said : #1

Any custom package that isn't taken directly from Ubuntu/Debian's repositories can be found at our mini-repository at http://archive.turnkeylinux.org, and the corresponding source can be found at http://code.turnkeylinux.org

For more information regarding development please see: http://www.turnkeylinux.org/community/development

I hope the above is what you are looking for, if not, let us know.

Alon Swartz (alonswartz) said : #2

This is more of a question than a bug.

Any custom package that isn't taken directly from Ubuntu/Debian's repositories can be found at our mini-repository at http://archive.turnkeylinux.org, and the corresponding source can be found at http://code.turnkeylinux.org

For more information regarding development please see: http://www.turnkeylinux.org/community/development

I hope the above is what you are looking for, if not, let us know.

Alon Swartz (alonswartz) said : #3

answer included as original bug comment

Frans van Berckel (fberckel) said : #4

Maybe i was not clear. To build the Turnkey sources, you need at least the .orig.tar.gz, the .dsc and sometimes a .diff.gz debian file. In a non x86 environment, are the binary .deb files not useful.

Alon Swartz (alonswartz) said : #5

You are correct with regards to Debian/Ubuntu distributed packages that are patched by the distribution. We found the process cumbersome, and because we use git internally, we opted to streamline the process and rely on git to handle all changes.

This might not be inline with so-called best-practices, or even the debian policy, but after weighing the pros vs. cons, we opted for our streamlined approach. This ofcourse is not set in stone, and if collaboration from the community requires change in process, we are open to suggestions.

BTW, we have received several requests to provide an easier way to download and collaborate on the code, so selected projects have been uploaded to http://github.com/turnkeylinux (with their full git history), as described in this forum post: http://www.turnkeylinux.org/forum/general/20091103/selected-code-now-hosted-github

Note that the published source on both github and code.turnkeylinux.org can be built as-is (with the only exception of changelog, which as described earlier, we rely on git).

Can you help with this problem?

Provide an answer of your own, or ask Frans van Berckel for more information if necessary.

To post a message you must log in.