[EN] 32 bit paintitblack?

[michaa7]

I absolutely have no clue how much work it would be to fire up your build machinery and configure it appropriately for a 32 bit paintitblack.iso, but I'd like the idea of a not so outdated iso for my architekture ...

[piper]

You can make one yourself

git clone git://git.siduction.org/.../pyfll.git

[michaa7]

seriously? No need to dive into the abyss of whateverconfig or scripting?

Simply execute command and wait some hours (here on my sempron  lowend machinery)?

[piper]

seriously? No need to dive into the abyss of whateverconfig or scripting?

Simply execute command and wait some hours (here on my sempron  lowend machinery)?

seriously ! so basically you want someone else to do it for you (waiting hours), I don't even own a 32 bit machine, the best I can do is to make a 32/64 bit iso, so then you have a choice, again, It would  take time to build it.

Back in time before I had a 64bit, I use to take the time to build on my 32 bit machine, it's not as bad as you are making it out to be, and in the process you get to learn a little/lot.

It's a good feeling installing something you built, whether it is stock or customized to your liking 

[michaa7]

seriously? No need to dive into the abyss of whateverconfig or scripting?

Simply execute command and wait some hours (here on my sempron  lowend machinery)?

seriously ! so basically you want someone else to do it for you (waiting hours),...

No, that was not my intention, and yeah, I would learn a lot. I think I'll give it a try. But one last question: How much space do I need for git data and iso all together approximately. I assume I'd do it as normal user in my home? And re time, how many hours should I expect to wait (sempron 2900, 1 GB RAM) 2h? 5h? 10h? overnight?

[towo]

There is no need to do that on a 32bit machine. A 32bit iso can be build on a 64bit machine.

[michaa7]

Thanks towo.

That is very usefull info as this means I could use my laptop (much more RAM and CPU power). But the HD-space is limited. So how much disk space should I reserve for git plus ISO?
And I certainly would need to read at least how to configure the built of a 32 bit ISO on a 64 bit computer. What do I first need to read?

[piper]

3-5 gigs should be plenty for 1 iso & git  (stock)

git folder (pyfll)  = 2.0 MiB  (272 files, 32 sub-folders)

Even my custom is only 3.4 gigs

[towo]

And I certainly would need to read at least how to configure the built of a 32 bit ISO on a 64 bit computer. What do I first need to read?

You should first have a look in fll.conf, then it should be clear.

[michaa7]

thanks to both of you, I'll give it a try soon.

[ReinerS]

Hmm, I got problems trying that:

Code: [Select]

root@HP615RS:/usr/src# git clone git://git.siduction.org/.../pyfll.git
Klone nach 'pyfll'...
fatal: remote error: access denied or repository not exported: /.../pyfll.git
Any idea what I did wrong ?

regards

Reiner

[towo]

1. Never checkout sourcecode as root!
2. git clone git://git.siduction.org/code/pyfll.git

[ReinerS]

@towo: Ok, thank you for the info.


regards

Reiner

[michaa7]

I now installed git on my laptop and will checkout soon.

should I install one/some/all of the suggested files? If so, possibly provide why I should do so.

git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn

Up to now I have installed git without any suggested or recommended package.



I have created a new partition labeled "git" which I mount with defaults into /home/<user>/git

I assume I go to this directory when I checkout and execute the command which you posted above. Or is it advisable to do it somehow differently?

Some more questions:
Is
http://wiki.siduction.de/index.php?title=Erstellen_eines_siduction-%C3%A4hnlichen_ISO
still valid?

What happens in build_dir = /media/fll/build_dir/ ?
The wiki says I don't need pbuilder, but if I use it, how do I have to configure build_dir ? And is the build process aware of my local /var/cache/apt/archives ? I don't want to redownload all those packages again.

What does fll and pyfll mean? Over the years I saw these expressions again and agian without having a clue what they mean. What those letters stand for? Could someone enlighten me?

It is not that simple to understand what to do, but step by step I think I understand what I have to configure, but it's not always obvious.

Thanks so far, infos to my questions would be very appreciated.

n8

[VladimirVilimaitis]

I wonder what prevents developers from releasing x86 binaries? Considering that it will be, as some have said earlier in this thread "only a couple of hours of waiting" it seems to be a huge downside to have support for all but one of their x86 images only due to the lack of the last needed step.
This dissapoints me, as I have specifically looked for a distribution that supports LxQt natively and I almost found it in Siduction, yet still I am limited by my hardware.