Staying GPL compliant

Non release banter
User avatar
agreimann
Samurai
Samurai
Posts: 137
Joined: 19 Apr 2011, 21:09
Location: U.S.

Re: Staying GPL compliant

Post#16 by agreimann » 07 Jun 2011, 19:21

@Hamza: Yep. I think we're honestly getting there.

User avatar
agreimann
Samurai
Samurai
Posts: 137
Joined: 19 Apr 2011, 21:09
Location: U.S.

Re: Staying GPL compliant

Post#17 by agreimann » 21 Jun 2011, 17:54

Remember, we need to get our sources out once 1.0 is released, so that Porteus will stay trouble-free with the GPL world! Thanks, all and go Porteus!

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Staying GPL compliant

Post#18 by Ahau » 28 Jun 2011, 16:51

fanthom wrote:@agreimann
Porteus code is still evolving as we are in rc stage. just added a function to linuxrc which discovers if booting media is removable, if not then in case of doing 'copy2ram' hard drive partition is not unmounted (no point for this).
When 1.0 is out we can gather all scripts in one tarball and post on the main site.

Thanks for suggestion.
Just a reminder (due to a request on mchat) about this task, now that V1.0 is out (of course, we may want to wait until some more bugs/fixes shake out!).
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
fanthom
Site Admin
Site Admin
Posts: 4618
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Staying GPL compliant

Post#19 by fanthom » 28 Jun 2011, 20:44

give me some extra time as brokenman was out last few days before 1.0 and we need to sync our 32/64 trees.
then we can prepare a tarball and upload it on the site.
Please add [Solved] to your thread title if the solution was found.

Sitwon
White ninja
White ninja
Posts: 16
Joined: 27 Jun 2011, 21:24
Location: Silver Spring, MD USA

Re: Staying GPL compliant

Post#20 by Sitwon » 29 Jun 2011, 20:07

fanthom wrote:give me some extra time as brokenman was out last few days before 1.0 and we need to sync our 32/64 trees.
then we can prepare a tarball and upload it on the site.
I'm very eager to see how your build tree is setup. It should help me figure out how to layout my own build environment.

Most of your modules seem to be composed of Slackware packages, and in those cases I can just look in /var/log/packages to see what is necessary to re-build them, but in some cases you didn't use Slackware-style packages leaving me more or less guessing at what was done.

I know that squashfs-tools didn't come from a Slackware package because there isn't one. I just submitted a SlackBuild to SBo this morning.
https://github.com/Sitwon/SlackBuilds/t ... shfs-tools

That still leaves a bunch of assorted files/scripts like /opt/porteus-scripts and liblinuxlive which are untracked by pkgtools. I'm going to try writing a script tonight to see if I can find any more untracked files.

Aside from the base modules (which are over 1GB when unpacked) I have checked the rest of my build environment into a git repo.
https://github.com/Sitwon/Porteus

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Staying GPL compliant

Post#21 by brokenman » 30 Jun 2011, 12:50

Sitwon,

This is a little off topic and not related to GPL.

Essentially we acquire slackware packages (e.g 001-core.xzm base module packages) and unpack somewhere. There are some custom modules that are compiled locally on Porteus that are added. A cleanup script is run to remove unneeded files, the Porteus tree is added and the folder is packed to a module.

I statred a svn project a while ago, and found it too much trouble. Eventually i will restart it with only the Porteus tree, custom files, and a script to build Porteus, but this is a way down the track.

If you want any more info PM me.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4618
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Staying GPL compliant

Post#22 by fanthom » 01 Jul 2011, 20:21

Here is full Porteus 64bit tree:
http://ponce.cc/porteus/x86_64/current/ ... 11.tar.bz2

The tree contains all loose files which are not listed in /var/log/packages/* files (slackware/custom packages).
Tarball includes all updates and fixes merged till today.

BTW: Cleanup scripts are little messy (brokenman's one are well commented).

Hope someone find it useful.

If you have any queries/doubts (eg about GPL compatibility) - feel free to ask.

Regards,
fanthom
Please add [Solved] to your thread title if the solution was found.

Sitwon
White ninja
White ninja
Posts: 16
Joined: 27 Jun 2011, 21:24
Location: Silver Spring, MD USA

Re: Staying GPL compliant

Post#23 by Sitwon » 02 Jul 2011, 05:05

fanthom wrote:Here is full Porteus 64bit tree:
http://ponce.cc/porteus/x86_64/current/ ... 11.tar.bz2

The tree contains all loose files which are not listed in /var/log/packages/* files (slackware/custom packages).
Tarball includes all updates and fixes merged till today.

BTW: Cleanup scripts are little messy (brokenman's one are well commented).

Hope someone find it useful.

If you have any queries/doubts (eg about GPL compatibility) - feel free to ask.

Regards,
fanthom
Perfect, this looks like exactly what I was looking for. It might take me a couple days to integrate this into my tree but it'll be much easier now than trying to reverse your xzm packages.

Thanks.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Staying GPL compliant

Post#24 by brokenman » 04 Jul 2011, 13:48

Here is the full 32bit tree. I've included a list of all custom compiled modules, but have not included the modules themselves.

http://ponce.cc/porteus/i486/current/ex ... 01.tar.bz2
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply