i have just become aware of the slackports project, and i'm really happy that someone has started it. Many people were leaving slackware to the (nice) gentoo distibution because of portage, and that was a thing i always thought would fit well in slack.
well, i've just downloaded slackports and skimmed through the script (without paying too much attention :), and i have some suggestions:
1) do md5sums of the downloaded tarballs
2) change the "if [ $lang = "FR" ]; then... else..." to a function which would get the translations on a file acording to users preferences (a config file maybe?)
3) re-write it in perl for the more advanced features (and speed) if compared to bash (hmm... probabably i would reject that, because it would require perl in some small installations that otherwise wouldn't use it, like in firewalls.)
well, that's it. if you want, i can offer my spare time to help (though that isn't much ;), as i have some experience with bash scripting and perl.
congrats for the initiative!!
andre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the md5sum, i have suggested this point to baptux and i think it will be implemented quickly, but i think we will make a ROADMAP rapidly to fix the futur of the developement , improve ideas, and help persons who would like to contribute.
For the language translation, we have received a perl line to simplify language support in separate files, and i have modified the slackports code to implement a /etc/rc.conf config file to store compilation and specific options and some other parameters we would like to implement. I have implemented rsync support to make easy and lightly ports update.
For the language, i think we will use shell script with some perl, but not perl-only language because we would like to implement an easy to modify solution, and to run slackports on most configurations, including non-perl hosts (and because we have more experience in shell script, and personally i am a perl newbie :)
I would like to implement a perl solution for persons who would like to run slackports with no wget or rsync installed (i will probably use perl and especially Rsync module)
For the moment, we would like to organize developpement, but we would be happy to have some help :)
Thaks for your interest, suggestions, and your help.
Ludo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi
i have just become aware of the slackports project, and i'm really happy that someone has started it. Many people were leaving slackware to the (nice) gentoo distibution because of portage, and that was a thing i always thought would fit well in slack.
well, i've just downloaded slackports and skimmed through the script (without paying too much attention :), and i have some suggestions:
1) do md5sums of the downloaded tarballs
2) change the "if [ $lang = "FR" ]; then... else..." to a function which would get the translations on a file acording to users preferences (a config file maybe?)
3) re-write it in perl for the more advanced features (and speed) if compared to bash (hmm... probabably i would reject that, because it would require perl in some small installations that otherwise wouldn't use it, like in firewalls.)
well, that's it. if you want, i can offer my spare time to help (though that isn't much ;), as i have some experience with bash scripting and perl.
congrats for the initiative!!
andre
Hi,
For the md5sum, i have suggested this point to baptux and i think it will be implemented quickly, but i think we will make a ROADMAP rapidly to fix the futur of the developement , improve ideas, and help persons who would like to contribute.
For the language translation, we have received a perl line to simplify language support in separate files, and i have modified the slackports code to implement a /etc/rc.conf config file to store compilation and specific options and some other parameters we would like to implement. I have implemented rsync support to make easy and lightly ports update.
For the language, i think we will use shell script with some perl, but not perl-only language because we would like to implement an easy to modify solution, and to run slackports on most configurations, including non-perl hosts (and because we have more experience in shell script, and personally i am a perl newbie :)
I would like to implement a perl solution for persons who would like to run slackports with no wget or rsync installed (i will probably use perl and especially Rsync module)
For the moment, we would like to organize developpement, but we would be happy to have some help :)
Thaks for your interest, suggestions, and your help.
Ludo
all right, i'll keep visiting the project site, waiting for the ROADMAP to come :)
please feel free to email me if you need any help