[opt-cross] New ports added.
New ports on opt-cross (eabi): libattr libcap nfs-utils --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org
Hi Victor, On 05/14/10 20:49, pitillo@crux-arm.nu wrote:
New ports on opt-cross (eabi): libattr libcap nfs-utils nice! I also added smpeg which worked fine on jornada's devices where mplayer didn't run
Regards, -- Jose V Beneyto | http://sepen.mine.nu/
On 05/15/10 11:10, Jose V Beneyto wrote:
Hi Victor,
On 05/14/10 20:49, pitillo@crux-arm.nu wrote:
New ports on opt-cross (eabi): libattr libcap nfs-utils nice! I also added smpeg which worked fine on jornada's devices where mplayer didn't run 2 new ports added: giblib feh
Regards, -- Jose V Beneyto | http://sepen.mine.nu/
On 05/15/10 11:47, Jose V Beneyto wrote:
On 05/15/10 11:10, Jose V Beneyto wrote:
Hi Victor,
On 05/14/10 20:49, pitillo@crux-arm.nu wrote:
New ports on opt-cross (eabi): libattr libcap nfs-utils nice! I also added smpeg which worked fine on jornada's devices where mplayer didn't run 2 new ports added: giblib feh
Regards,
Added those packages (smpeg, giblib and feh) to eabi collection. What do you think about making a new post in every new port we add to eabi/no-eabi collections? In this way we can know when is added a port to one collection and in we can keep track of them in the thread, answering telling that the other (the one who didn't make the notify to the ML) just builded them and uploaded to the collecion (eabi or no-eabi). May be we can adopt a template for the subject of those threads, putting the names of the updated ports in the subject too. I hope this can be interesting to let other know when a new port is added. Regards, Victor. -- Learning bit by bit. Victor Martinez | http://lokalix.dyndns.org
On 05/15/10 12:47, Victor Martinez wrote:
[...]
What do you think about making a new post in every new port we add to eabi/no-eabi collections? In this way we can know when is added a port to one collection and in we can keep track of them in the thread, answering telling that the other (the one who didn't make the notify to the ML) just builded them and uploaded to the collecion (eabi or no-eabi). neat, +1 May be we can adopt a template for the subject of those threads, putting the names of the updated ports in the subject too.
I hope this can be interesting to let other know when a new port is added.
well, we can try to run a post-commit hook for git, so when a word "[new port]" appears as a part of the commit message the hook script should send a mail to our ML, like crux.nu has for the word "[notify]" In the future we could try to add more words ([new port], [notify], [bug], etc...) to the hook script, what do you think about? Regards, -- Jose V Beneyto | http://sepen.mine.nu/
On 05/15/10 13:01, Jose V Beneyto wrote:
On 05/15/10 12:47, Victor Martinez wrote:
[...]
What do you think about making a new post in every new port we add to eabi/no-eabi collections? In this way we can know when is added a port to one collection and in we can keep track of them in the thread, answering telling that the other (the one who didn't make the notify to the ML) just builded them and uploaded to the collecion (eabi or no-eabi). neat, +1 May be we can adopt a template for the subject of those threads, putting the names of the updated ports in the subject too.
I hope this can be interesting to let other know when a new port is added.
well, we can try to run a post-commit hook for git, so when a word "[new port]" appears as a part of the commit message the hook script should send a mail to our ML, like crux.nu has for the word "[notify]" In the future we could try to add more words ([new port], [notify], [bug], etc...) to the hook script, what do you think about?
I think that's a very good idea. I didn't thought about it. Another task "todo". Great idea Jose.
Regards,
Regards, Victor. -- Learning bit by bit. Victor Martinez | http://lokalix.dyndns.org
participants (3)
-
Jose V Beneyto
-
pitillo@crux-arm.nu
-
Victor Martinez