Jump to content

skunk

Members
  • Content Count

    27
  • Joined

  • Last visited

Everything posted by skunk

  1. hey! i'm 50% italian, but i don't live in italy anymore since 20 years... and oh, since yesterday i've switched back to the gentoo's portage tree after 6+ years with funtoo so i think i don't count anymore... cheers!
  2. While setting an empty GENTOO_MIRRORS makes portage use gentoo's mirrors with way better network performance, you may now either miss some package or size/sum mismatch any other... After some tests I've found out that: sometimes the download speed is as slow as 56kbps when this happens downloads from remote networks are still decently speedy (tried from data centers in the US and EU) running local speedtest with other servers in Santa Fe (where the fastpull server is located) don't show the same slow down I live in Granada and I think my ISP (Movistar/Telefonica)
  3. i don't know if it's wise to get rid of gcc-6.4.0 that fast since the most recent versions of cuda sdk/toolkit still depends on it as gcc versions later than 6 are not supported. however i can confirm that forcing compilation of cuda depending applications (like net-p2p/xmr-stak or app-crypt/johntheripper) by replacing "#if __GNUC__ > 6" with "#if __GNUC__ > 7" on /opt/cuda/include/crt/host_config.h:119, didn't give me any compilation or runtime problem so far... so please either leave gcc 6 ebuild alone or patch dev-util/nvidia-cuda-toolkit to ignore upstream unsupported gcc 7
  4. https://bugs.funtoo.org/browse/FL-4888
  5. hello, any chance to get safe chromium ebuild to the tree? thank you
  6. if you don't want to downgrade and keep staying up to date with kde-kit's stuff, this is what i did: # check out gentoo's tree: cd /var/git git clone git://anongit.gentoo.org/repo/gentoo.git # create a script that syncs kde-kit's stuff from the gentoo's tree to a local overlay: cat > /root/sync_kde.sh #!/bin/bash cd /var/git/gentoo git pull cd /var/git/meta-repo/kits/kde-kit for i in *-* do [[ ! -d /usr/local/portage/kde/$i ]] && mkdir /usr/local/portage/kde/$i cd $i for j in * do [[ -d /var/git/gentoo/$i/$j ]] && rsync
  7. nevermind it doesn't work the way i've thought, i've created my own overlay instead...
  8. i've created my own kde-kit branch, how can i mark it active so that it might be chosen from ego.conf please? thank you
  9. ok, i can live with it for some time, however why forcing everybody on 5.10-prime branch if they where on master if neither branch won't get updates anymore? downgrading from master to 5.10-prime isn't something worth doing if you already are on plasma-5.11.1/apps-17.08.2/framework-5.39, imho...
  10. hello again, i've the following set into my ego.conf: xorg-kit = 1.19-prime media-kit = 1.1-prime kde-kit = master however on today sync i've got this message: "Kit kde-kit branch master specified in ego.conf is not currently active; using default kit instead." so why can i not choose kde-kit's master branch anymore in ego.conf? i've forced the master branch checkout by adding: @git -C /home/meta-repo/kits/kde-kit checkout origin/master || true into eix-sync.conf, however i wonder why these kind of hacks are necessary... thank you
  11. skunk

    kits logic

    well yes, would be nice to have the possibility to choose between kde-plasma-release and kde-plasma-lts... however if it's too much fuss, just branch using kde-apps as reference instead of kde-desktop...
  12. skunk

    kits logic

    i'm pretty sure they actually do it since one component release can be quite far away (in terms of time) from the other...
  13. skunk

    kits logic

    what do you mean exactly with updating kde parts asynchronously? kde-apps/frameworks/plasma have different independent release schedules and gentoo adds new ebuild short after there is a release of any of the 3 components afaik...
  14. skunk

    kits logic

    it would also be very cool to have an lts branch (like eg.18.08.3-lts-prime) which would install latest kde-apps-18.08.3 with kde-desktop-5.12.7 instead of kde-desktop-5.13.5 like 18.08.3-prime would do...
  15. skunk

    kits logic

    well... none... :) if you ask me, i would better branch on kde-apps version instead of kde-desktop version and number it as follows: 17.08.3-prime which includes kde-apps-17.08.3 (due nov. 6) kde-desktop-5.10.5 (released) kde-framework-5.40 (due nov. 4) 17.12.3-prime which includes kde-apps-17.12.3 (due march 8) kde-desktop-5.11.5 (due jan. 2) kde-framework-5.whatever on march 8 18.04.3-prime which includes kde-apps-18.04.3 (due sometime in july) kde-desktop-5.12.6 (due june 20) kde-framework-5.whatever in july branching it on kde-desktop version would need to push kd
  16. skunk

    kits logic

    thank you daniel for your explication, kde software compilation, how it's called today, consists of 3 components: kde-framework: with a monthly release schedule which may include both bugfixes and new features, since there are no minor versions, it may be snapshotted at any time kde-plasma: with frequent minor releases (for bugfixes) and a new major release every 5-6 months, since there usually are just 5 minor versions (except from lts releases), taking a snapshot when it reach a 5.x.5 version it would make an ideal point for a prime release kde-apps: with about month
  17. skunk

    kits logic

    so in my kde-kit example shall i expect a new, let's say, 5.10-prime-r1 branch with kde-apps-17.08.2 or will it only (kde-apps-17.08.2) be available into the new 5.11-prime branch? if the latter it would be very unfortunate for someone wanting to stay stable (keep on plasma 5.10 while getting apps 17.08 bugfixes)... thank you
  18. skunk

    kits logic

    hello devs (oleg) :) i wonder what are the rules behind this new kit organization... do packages from the master branch eventually make into a prime branch or are prime branches virtually immutable? if the former, after lying into the the master branch for some time (like gentoo's stable/unstable)? how long? any other criterion instead? if the latter, are "stable users" supposed to jump from prime-n to prime-n+1 branches at their discretion? for example i'm on the default 5.10-prime kde-kit's branch and i see that kde-plasma-5.11.0, kde-frameworks-5.39 and kde-apps-17.08.2 were added t
  19. ok, feeding emerge with the packages to build worked for me too even without unmerging qt-5.7.1 (useful if you don't want to stop using your pc meanwhile or if you want to keep a still needed qt4 installation)... i wonder if the conflicts was just a portage invention... :huh:
  20. yet more conflicts; # emerge -uDN world These are the packages that would be merged, in order: Calculating dependencies... done! Oops! Conflicts have been encountered: >>> dev-qt/qtsql-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qtsvg-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/designer-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>> dev-qt/qttest-5.9.2:5/5.9::dev-kit, ebuild scheduled for merge, wants ~dev-qt/qtcore-5.9.2 >>&g
  21. ok, i won't use backtrack never again... no, there's no traces of those packages in my world file...
  22. already was to portage-2.3.8-r6 and i've added the backtrack option to see if the conflict get solved, however the outcome is identical...
  23. hello, i notice the conflicts messages have changed and now i cannot interpret them anymore: # emerge -uDN world --backtrack=1000 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/protobuf-3.4.1:0/14::dev-kit [3.3.0:0/13::dev-kit] USE="zlib -emacs -examples -static-libs {-test} (-java%) (-python%*)" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="(-python2_7%*) (-python3_4%*) (-python3_5%) (-python3_6%)" 4,385 KiB [ebuild R ] dev-libs/protobuf-c-1.3.0:0/1.0.0::dev-kit USE="-static-libs {-test}" ABI_X86="(64) -32 (-x32)" 4
  24. skunk

    eix and kits

    thank you cafaia, adding @emerge --metadata || true did the trick (the rest was already there) a hint: also adding @ego sync will just require eix-sync to sync the kit tree...
×
×
  • Create New...