diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20121010 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121010')
8 files changed, 90 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment-0001.html new file mode 100644 index 000000000..c5e6bb031 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment-0001.html @@ -0,0 +1,21 @@ +<div class="gmail_quote">2012/10/8 Manuel Hiebel <span dir="ltr"><<a href="mailto:manuel.mageia@hiebel.eu" target="_blank">manuel.mageia@hiebel.eu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Le 08/10/2012 15:27, Nicolas Lécureuil a écrit :<div><div class="h5"><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hi,<br> +<br> +is there any plans to add grub2 support ? is there someone already working on<br> +it ?<br> +<br> +regards,<br> +<br> +Nicolas.<br> +</blockquote> +<br></div></div> +PoK started something in Mandriva with the classical installer, maybe Rosa too.<br> +</blockquote></div>Indeed!<div><br></div><div>While I had hopes of us getting our first beta ready soon, I've decided to postpone it, very much due to running late with grub2 stuff, which it some of the features that I have on my *MUSTDO* list and I find crucial to have ready for deployment in time for a beta candidate.</div> +<div>So far I've only switched the installer to use grub2 (and unfortunately my work on the installer won't be that easy for you to merge and benefit from as I've done some heavy work on cleaning up, sanitizing and rewriting the tools to create the installer in python, for which the python code is rather modest, but this is very much due to heavy work and improvements on the distribution core in advance and also tied into various new rpm functionality that I've implemented myself and that there's been next to zero interest in from anyone at Mageia. So unfortunately I don't see it as very realistic to see any of it making it into Mageia, despite the obvious mutual benefits, poltics keeps getting in the way..</div> +<div><br></div><div>For ROSA they migrated to grub 2 a somewhat while ago, their work can most likely be picked up and more easily be reused by yourself as the required changes in drakx has been done already in a drakx branch with relatively few changes commited to it, likely making it fairly trivial to merge.</div> +<div><br></div><div>Personally I'm not sure if I'll go with the same approach as ROSA and upstream grub encourages by default, but would rather have a grub configurantion entry shipped with each kernel package, ie. like a . /boot/grub2/cfg.d directory where one could put like /boot/grub2/cfg.d/3.4.1-1.4-desktop.grub which houlds the config with kernel and initrd images, which gets automatically read by grub without having to regenerate whole grub2 configuration each time a new package gets installed.</div> +<div>This would also free one from any special tools and script to handle this for each and every kernel as is the situation today..</div><div>This would also be quite distribution neutral as well. :)</div><div><br></div> +<div>I'm not sure of what use this might actually be or even if any at any sense for others to try grasp, but I hope to have grub 2 migration more or less working in a week or so, I've decided to push a second alpha as soon as I'm done with my work on the installer for this round, then hopefully a beta 2 should be about ready in a couple more weeks or so..</div> +<div><br></div><div>Don't hesitate asking any questions if you have any interest in my work on these things. :)</div><div><br></div><div>--</div><div>Regards,</div><div>Per Øyvind</div> diff --git a/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment.html b/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment.html new file mode 100644 index 000000000..c5e6bb031 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/2e45e640/attachment.html @@ -0,0 +1,21 @@ +<div class="gmail_quote">2012/10/8 Manuel Hiebel <span dir="ltr"><<a href="mailto:manuel.mageia@hiebel.eu" target="_blank">manuel.mageia@hiebel.eu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Le 08/10/2012 15:27, Nicolas Lécureuil a écrit :<div><div class="h5"><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hi,<br> +<br> +is there any plans to add grub2 support ? is there someone already working on<br> +it ?<br> +<br> +regards,<br> +<br> +Nicolas.<br> +</blockquote> +<br></div></div> +PoK started something in Mandriva with the classical installer, maybe Rosa too.<br> +</blockquote></div>Indeed!<div><br></div><div>While I had hopes of us getting our first beta ready soon, I've decided to postpone it, very much due to running late with grub2 stuff, which it some of the features that I have on my *MUSTDO* list and I find crucial to have ready for deployment in time for a beta candidate.</div> +<div>So far I've only switched the installer to use grub2 (and unfortunately my work on the installer won't be that easy for you to merge and benefit from as I've done some heavy work on cleaning up, sanitizing and rewriting the tools to create the installer in python, for which the python code is rather modest, but this is very much due to heavy work and improvements on the distribution core in advance and also tied into various new rpm functionality that I've implemented myself and that there's been next to zero interest in from anyone at Mageia. So unfortunately I don't see it as very realistic to see any of it making it into Mageia, despite the obvious mutual benefits, poltics keeps getting in the way..</div> +<div><br></div><div>For ROSA they migrated to grub 2 a somewhat while ago, their work can most likely be picked up and more easily be reused by yourself as the required changes in drakx has been done already in a drakx branch with relatively few changes commited to it, likely making it fairly trivial to merge.</div> +<div><br></div><div>Personally I'm not sure if I'll go with the same approach as ROSA and upstream grub encourages by default, but would rather have a grub configurantion entry shipped with each kernel package, ie. like a . /boot/grub2/cfg.d directory where one could put like /boot/grub2/cfg.d/3.4.1-1.4-desktop.grub which houlds the config with kernel and initrd images, which gets automatically read by grub without having to regenerate whole grub2 configuration each time a new package gets installed.</div> +<div>This would also free one from any special tools and script to handle this for each and every kernel as is the situation today..</div><div>This would also be quite distribution neutral as well. :)</div><div><br></div> +<div>I'm not sure of what use this might actually be or even if any at any sense for others to try grasp, but I hope to have grub 2 migration more or less working in a week or so, I've decided to push a second alpha as soon as I'm done with my work on the installer for this round, then hopefully a beta 2 should be about ready in a couple more weeks or so..</div> +<div><br></div><div>Don't hesitate asking any questions if you have any interest in my work on these things. :)</div><div><br></div><div>--</div><div>Regards,</div><div>Per Øyvind</div> diff --git a/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment-0001.asc new file mode 100644 index 000000000..12e176b97 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQdXFET1rWTfpocyQRAkjzAJwMjonhLav61sHGIfi/3JMBLSlsBwCgrRtC +zVCJ1yR+NepiVJ1zHnMnidQ= +=mr/g +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment.asc b/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment.asc new file mode 100644 index 000000000..12e176b97 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/69fb5828/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQdXFET1rWTfpocyQRAkjzAJwMjonhLav61sHGIfi/3JMBLSlsBwCgrRtC +zVCJ1yR+NepiVJ1zHnMnidQ= +=mr/g +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment-0001.asc new file mode 100644 index 000000000..ea0cc9415 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQdVndT1rWTfpocyQRAqZpAKCPjVoohr37fULrghRoGGZaxGtgFACfYWQT +NZEo1EHrMmfb1+ad2a3MRew= +=DI6Q +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment.asc b/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment.asc new file mode 100644 index 000000000..ea0cc9415 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/a659c89e/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQdVndT1rWTfpocyQRAqZpAKCPjVoohr37fULrghRoGGZaxGtgFACfYWQT +NZEo1EHrMmfb1+ad2a3MRew= +=DI6Q +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment-0001.html new file mode 100644 index 000000000..b49ca2ef3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment-0001.html @@ -0,0 +1,10 @@ +<div class="gmail_quote">2012/9/30 Steven Tucker <span dir="ltr"><<a href="mailto:tuxta2@gmail.com" target="_blank">tuxta2@gmail.com</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> + +If it was my language of choice I would be writing it in C++. It was 100% due to discussions on the list and in IRC that led to writing it in Perl. As noted, I have previously never written any Perl, and so it would not have been my first or even second choice, I did it purely because of the feedback I received from the Mageia community.<br> +</blockquote><div>Perl is a dead-end, and most of the code is horrible even by perl standards, we've been started on rewriting a lots of the code for drakx in mandriva, some of the progress has been rather slow, but things are</div> +<div>moving at least, where I've already rewritten much of the perl specific parts of it has been rewritten in C & shell so far, with some of the tools to generate the installer isos being rewritten in python so far.</div> +<div><br></div><div>What I'm intending to target is more of some new libraries for the purpose (ie. the backend), preferrably written in C++, whileas higher level functionality such as gui matters would have ie. some python bindings provided as well.</div> +<div><br></div><div>It's not really *that* much code that needs to be rewritten, the worst part is to try dechiffer and wasting more time spent on trying to understand the code than just writing the code once you know how to do it.</div> +<div><br></div><div>The drakx tools's perl code should really be considered as legacy, I can't think of anyone who has deeper insight on it who'd ever find anything but som sentimental value from it..</div><div> +<br></div><div>If you'd have any interest in any of this, don't hesitate to get in touch. :)</div><div><br></div><div>PS: considering your drakx branch is a fork of the original upstream drakx project and that these two have heavily diverged since, established etiquete would dictate that the forket project should change..</div> +<div><br></div><div>--</div><div>Regards,</div><div>Per Øyvind</div></div> diff --git a/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment.html b/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment.html new file mode 100644 index 000000000..b49ca2ef3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121010/da07db6c/attachment.html @@ -0,0 +1,10 @@ +<div class="gmail_quote">2012/9/30 Steven Tucker <span dir="ltr"><<a href="mailto:tuxta2@gmail.com" target="_blank">tuxta2@gmail.com</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> + +If it was my language of choice I would be writing it in C++. It was 100% due to discussions on the list and in IRC that led to writing it in Perl. As noted, I have previously never written any Perl, and so it would not have been my first or even second choice, I did it purely because of the feedback I received from the Mageia community.<br> +</blockquote><div>Perl is a dead-end, and most of the code is horrible even by perl standards, we've been started on rewriting a lots of the code for drakx in mandriva, some of the progress has been rather slow, but things are</div> +<div>moving at least, where I've already rewritten much of the perl specific parts of it has been rewritten in C & shell so far, with some of the tools to generate the installer isos being rewritten in python so far.</div> +<div><br></div><div>What I'm intending to target is more of some new libraries for the purpose (ie. the backend), preferrably written in C++, whileas higher level functionality such as gui matters would have ie. some python bindings provided as well.</div> +<div><br></div><div>It's not really *that* much code that needs to be rewritten, the worst part is to try dechiffer and wasting more time spent on trying to understand the code than just writing the code once you know how to do it.</div> +<div><br></div><div>The drakx tools's perl code should really be considered as legacy, I can't think of anyone who has deeper insight on it who'd ever find anything but som sentimental value from it..</div><div> +<br></div><div>If you'd have any interest in any of this, don't hesitate to get in touch. :)</div><div><br></div><div>PS: considering your drakx branch is a fork of the original upstream drakx project and that these two have heavily diverged since, established etiquete would dictate that the forket project should change..</div> +<div><br></div><div>--</div><div>Regards,</div><div>Per Øyvind</div></div> |