taskSavannah Administration - Tasks: task #9772, Submission of Crossplex

 
 

task #9772: Submission of Crossplex

Submitter:  David Wuertele <wuertele>
Submitted:  Tue 06 Oct 2009 06:26:57 PM UTC
   
 
Should Start On:  Tue 06 Oct 2009 12:00:00 AM UTC Should be Finished on:  Fri 16 Oct 2009 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  nicalvaro Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 22 Oct 2009 11:42:31 AM UTC, comment #4: 

I am trying to ask is there any specific dependency in the Linux kernel that would be required, that is not present in the Linux-libre version. From what I take it there is not. So I'll approve of the project.

> Is it a requirement that all savannah-hosted projects can build a Linux-libre kernel?


Since there are non-free issues with the Linux kernel, I think so.  I've asked another administrator and he said Linux-libre compatibility would be good. The linux kernel issue, I think is mainly hardware blobs, so your project should be able to handle from what I understand of it.

I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

-Deleted Account- <nicalvaro>
Tue 20 Oct 2009 11:26:10 PM UTC, comment #3: 


> You never answered my question if this project will support Linux-libre.


Sorry, I guess I missed that question when I originally read your email.  Can you please help me understand what you mean by "will support Linux-libre"?

If you are asking whether my project (a series of make macros compatible with make-3.81) will perform in the same manner whether the host system running GNU make has a linux-libre kernel, my answer would be "I haven't tested it, but I have no reason to suspect that it would not work".

If you are asking whether my project will build embedded systems with the Linux-libre kernel, my answer would be "I haven't tested it, but if the Linux-libre makefiles have the same build targets that kernel.org linux has, it should work fine."

I designed these macros to be flexible, but I only tested them on GNU/Linux with make-3.81, targeting only the target systems that interested me:  those target systems use kernel.org linux and linux-mips linux for their kernels.  I don't have any experience with other kernels, and so I couldn't really build support for them into the macros.

If someone wants to add support to crossplex for building any other kernel, including Linux-libre, I have absolutely no problem with that.  There is nothing that would prevent them from doing so.

Is it a requirement that all savannah-hosted projects can build a Linux-libre kernel?

> You said in the e-mail "I don't mind changing references in my sources." On
> savannah we do require you to refer to speak about it as GNU/Linux. There are
> other places on nongnu.org where you are able promote your project such as
> your project page and your homepage should you choose to host it on
> nongnu.org.


Yes, I am fine referring to operating systems based on the Linux kernel and glibc as GNU/Linux.  I think that is totally appropriate, and if savannah requires it I will absolutely change my documentation to reflect that.

> I seemed to have missed the 'third party software'.
> Does this refer to software that is non-free?
> Does these scripts automatically download or install any non-free software?
> Which licenses are being spoken of here?


What my library does is define macros that make it easy to unpack, patch, build, stage, and install third-party software.  It does not download any software at all.  It does not have rules that are specifically included to support non-free software, however, there is nothing in my macros that prevent someone from using them on non-free software.  It would be impossible for my macros to determine whether the user was using them to patch non-free software in the same way that the GNU "cp" command does not determine whether a binary being copied was created from free or non-free software.

> "To be hosted on Savannah, your project must be free software, and it must be
> kept independent of any non-free software. The package must not refer the user
> to any non-free software; in particular, it must not automatically download or
> install any non-free software.


Crossplex satisfies this requirement.

> The program should deliver its full functionality and convenience on a
> completely free platform based on a free operating system, such as GNU/Linux,
> working entirely with other free software. Otherwise it would be an inducement
> to install non-free operating systems or other non-free software.


Crossplex satisfies this requirement.

> It is ok for the program to run on non-free platforms or non-free operating
> systems, and to work with well-known non-free applications, in addition to
> working with free software, provided it gives the free software at least as
> good support as it gives to other alternatives. In other words, at no time, in
> no way, should your program put free software users at a disadvantage compared
> to those willing to use proprietary software."


Good.  There is nothing I can do to prevent people using GNU make on a non-free operating system.  Any operating system that runs GNU make can use my software.

David Wuertele <wuertele>
Tue 20 Oct 2009 09:59:05 PM UTC, comment #2: 

You never answered my question if this project will support Linux-libre.

You said in the e-mail "I don't mind changing references in my sources." On savannah we do require you to refer to speak about it as GNU/Linux. There are other places on nongnu.org where you are able promote your project such as your project page and your homepage should you choose to host it on nongnu.org.

I seemed to have missed the 'third party software'.
Does this refer to software that is non-free?
Does these scripts automatically download or install any non-free software?
Which licenses are being spoken of here?

Our requirements state:

"To be hosted on Savannah, your project must be free software, and it must be kept independent of any non-free software. The package must not refer the user to any non-free software; in particular, it must not automatically download or install any non-free software.

The program should deliver its full functionality and convenience on a completely free platform based on a free operating system, such as GNU/Linux, working entirely with other free software. Otherwise it would be an inducement to install non-free operating systems or other non-free software.

It is ok for the program to run on non-free platforms or non-free operating systems, and to work with well-known non-free applications, in addition to working with free software, provided it gives the free software at least as good support as it gives to other alternatives. In other words, at no time, in no way, should your program put free software users at a disadvantage compared to those willing to use proprietary software."

https://savannah.gnu.org/register/requirements.php


-Deleted Account- <nicalvaro>
Thu 08 Oct 2009 08:56:27 PM UTC, comment #1: 

Hi,

"Linux" is just a kernel of a more complex system that we like to refer to as GNU/Linux, to emphasize the ideals of the Free Software movement.

Would you mind changing references to Linux as an OS to GNU/Linux and references as a kernel with "Linux kernel" to avoid confusion with the common misused term "Linux Distribution"?

For more information, see http://www.gnu.org/gnu/linux-and-gnu.html.

I would like to know if these scripts work using the linux-libre kernel project. This is to ensure that your project works with all free dependencies since the defacto Linux kernel contains non-free code and blobs.

http://www.fsfla.org/svnwiki/selibre/linux-libre/index.en

-Deleted Account- <nicalvaro>
Tue 06 Oct 2009 06:26:57 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


Registration Administration


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):



Registration Details


  • Name: Crossplex
  • System Name:  crossplex
  • Type: non-GNU software & documentation
  • License: GNU General Public License v2 or later





Description:

Configure, Build, and Release Embedded Linux Distributions with the Crossplex library of Make macros.

I designed Crossplex to solve a lot of problems that I have encountered building Linux-based products at various companies.  Here is a list of my (admittedly somewhat obsessive) requirements when it comes to building:

  • The build should be able to output all configurations simultaneously in unique segments of the output tree without interference.


  • All configuration should be contained in checked-in files.


  • Maintain third party software in original packaging (according to license).


  • Support build and use of multiple toolchains in a single build.


  • Specify build dependencies explicitly.


  • Maintain built objects in directories named for the configuration.



Tarball URL:

http://sites.google.com/a/crossplex.org/www/crossplex-1-0-tar-bz/crossplex-v2.0.tar.bz2?attredirects=0


David Wuertele <wuertele>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by nicalvaro (Posted a comment)
  • -email is unavailable- added by wuertele (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-10-22 nicalvaro StatusNone Done
        Percent Complete0% 100%
        Assigned toNone nicalvaro
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code