Hi all, new Crux user here! I waited for the 3.0 release because I wanted a 64 bit system and so far I like it. I would like to use weechat because I have a nice configuration for it already. So I got the Pkgfile from the nogagplz repository and compiled weechat 0.3.7. Unfortunately this release is pretty old and my configuration is not working correctly with it. I tried to create a new Pkgfile for weechat 0.4.0 myself but it didn't work. The weechat source package doesn't include a configure file - so I tried to use autoconf to generate one but there were errors about some undefined macros and the compile afterwards stopped immediately with errors. As you can see I am obviously not a developer ;-) So is there somebody that would be willing to create a Pkgfile for the current weechat release? Thanks a lot for your work and for this distro. Lars
On Fri, 25 Jan 2013 22:21:06 +0100 Lars von den Driesch wrote:
Hi all,
Hi.
As you can see I am obviously not a developer ;-) So is there somebody that would be willing to create a Pkgfile for the current weechat release?
Attached. Mind you, it is minimal, only has build dependencies (cmake, gnutls, libgcrypt), and it builds fine at 2.8 64bit. It will automagically enable and build support for scripts in the other languages that you have apart from perl,which is installed by default (python,ruby, whatever) so expect footprint mismatch. Also, check out release notes and changelog for any configuration changes in this version. http://www.weechat.org/files/releasenotes/ReleaseNotes-0.4.0.html http://www.weechat.org/files/changelog/ChangeLog-0.4.0.html
Thanks a lot for your work and for this distro.
Lars
Have fun. Pedja
Hi Pedja,
Attached. Mind you, it is minimal, only has build dependencies (cmake, gnutls, libgcrypt), and it builds fine at 2.8 64bit. It will automagically enable and build support for scripts in the other languages that you have apart from perl,which is installed by default (python,ruby, whatever) so expect footprint mismatch. Also, check out release notes and changelog for any configuration changes in this version.
http://www.weechat.org/files/releasenotes/ReleaseNotes-0.4.0.html http://www.weechat.org/files/changelog/ChangeLog-0.4.0.html
Have fun.
Pedja
:-) Thank you very much for this! The port builds fine on 3.0 as well. I assume weechat still depends on ncurses :-) So I think it should also be added to the Pkgfile. The old Pkgfile for weechat-0.3.7 is also mentioning gtk and guile as dependency. I assume gtk can be skipped as the dev documentation mentions the gtk-ui as "not working" - but what about guile? Maybe nogagplz would like to put this into his repo... Again, thank you very much Lars
On Sat, 26 Jan 2013 18:35:39 +0100 Lars von den Driesch wrote:
Hi Pedja, :-) Thank you very much for this! The port builds fine on 3.0 as well.
Nice :)
I assume weechat still depends on ncurses :-) So I think it should also be added to the Pkgfile. The old Pkgfile for weechat-0.3.7 is also mentioning gtk and guile as dependency. I assume gtk can be skipped as the dev documentation mentions the gtk-ui as "not working" - but what about guile?
Dependencies from core repo, like ncurses, are rarely, or ever, listed in Depends line, iirc. The logic behind that is that you are supposed to have complete repo installed when you install Crux, since it contains the eh...core...of the system :) GTK ui is broken and not built by default, so no need for gtk dep, which is optional dependency anyway, same as guille. Only deps that are mandatory to build the port are listed in 'Depends line', optional deps are usually in the 'Nice to have' line. I would suggest that you start your personal repo, so you can make your own and modify ports as you like them, it is a great way to learn.
Again, thank you very much
np
Lars
Pedja
On Sat, Jan 26, 2013 at 07:23:05PM +0100, Predrag Ivanovic wrote:
On Sat, 26 Jan 2013 18:35:39 +0100 Lars von den Driesch wrote:
Hi Pedja, :-) Thank you very much for this! The port builds fine on 3.0 as well.
Dependencies from core repo, like ncurses, are rarely, or ever, listed in Depends line, iirc. The logic behind that is that you are supposed to have complete repo installed when you install Crux, since it contains the eh...core...of the system :)
Core ports are never listed.
I would suggest that you start your personal repo, so you can make your own and modify ports as you like them, it is a great way to learn.
Indeed. And when you feel like helping others, post your ports repo to http://crux.nu/portdb/ :) -- Fredrik Rinnestam
On Sat, Jan 26, 2013 at 09:43:43PM +0100, Fredrik Rinnestam wrote:
Dependencies from core repo, like ncurses, are rarely, or ever, listed in Depends line, iirc. The logic behind that is that you are supposed to have complete repo installed when you install Crux, since it contains the eh...core...of the system :)
Core ports are never listed.
Actually, they are (and i suck :)) "We list all runtime dependencies except for gcc (libstdc++) and glibc." http://crux.nu/Main/PortGuidelines -- Fredrik Rinnestam
On Sun, 27 Jan 2013 12:13:32 +0100 Fredrik Rinnestam wrote:
On Sat, Jan 26, 2013 at 09:43:43PM +0100, Fredrik Rinnestam wrote:
Dependencies from core repo, like ncurses, are rarely, or ever, listed in Depends line, iirc. The logic behind that is that you are supposed to have complete repo installed when you install Crux, since it contains the eh...core...of the system :)
Core ports are never listed.
Actually, they are (and i suck :))
"We list all runtime dependencies except for gcc (libstdc++) and glibc."
" - build dependencies provided by core are not listed in the dependency header - run-time dependencies from core which aren't dynamically linked in are not to be listed, either " So, we were sort of right ;) I need to brush up on all that build-time/runtime dependency distinction thingie.
participants (3)
-
Fredrik Rinnestam -
Lars von den Driesch -
Predrag Ivanovic