View previous topic :: View next topic |
Author |
Message |
asturm Developer
Joined: 05 Apr 2007 Posts: 8938
|
Posted: Thu Mar 18, 2010 6:32 pm Post subject: |
|
|
Yes, it won't work without manual work. geki has covered that in this thread. |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Thu Mar 18, 2010 8:25 pm Post subject: |
|
|
genstorm wrote: | Yes, it won't work without manual work. geki has covered that in this thread. |
oh, think that I got it now, thanks. Will try that later and see if I can get them to compile |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Fri Mar 19, 2010 3:42 pm Post subject: |
|
|
Seems that I am not able to get this working here
Am I right that the ebuilds should work just by inheriting boost-utils and adding add_boost_paths in configure, or is there anything else I have missed?
(Did the suggested cleanup actions for the 2 paths from the first post) |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Fri Mar 19, 2010 3:59 pm Post subject: |
|
|
SpectreDragon
yes, right. and hopefully before the actual configure script is called.
you may pastebin your content of the two paths (ls -l ...). _________________ hear hear |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Fri Mar 19, 2010 4:16 pm Post subject: |
|
|
geki wrote: | SpectreDragon
yes, right. and hopefully before the actual configure script is called.
you may pastebin your content of the two paths (ls -l ...). |
hope that is what you meant
Code: | spectred@PC-SPECTRED ~ $ ls -l /usr/include/ | grep -i boost
drwxr-xr-x 1 root root 10 Mar 19 16:14 boost-1_42
spectred@PC-SPECTRED ~ $ ls -l /usr/include/boost-1_42/ | grep -i boost
drwxr-xr-x 1 root root 4366 Mar 19 16:14 boost |
and /usr/include/boost-1_42/boost contains many header files, as expected
Code: | spectred@PC-SPECTRED ~ $ ls -l /usr/lib/ | grep -i boost
drwxr-xr-x 1 root root 778 Mar 19 16:21 boost-1_42
lrwxrwxrwx 1 root root 34 Mar 19 16:21 libboost_filesystem-1_42.so -> libboost_filesystem-1_42.so.1.42.0
lrwxrwxrwx 1 root root 34 Mar 19 16:21 libboost_filesystem-1_42.so.1 -> libboost_filesystem-1_42.so.1.42.0
lrwxrwxrwx 1 root root 34 Mar 19 16:21 libboost_filesystem-1_42.so.1.42 -> libboost_filesystem-1_42.so.1.42.0
-rwxr-xr-x 1 root root 84776 Mar 19 16:21 libboost_filesystem-1_42.so.1.42.0
lrwxrwxrwx 1 root root 37 Mar 19 16:21 libboost_filesystem-mt-1_42.so -> libboost_filesystem-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 37 Mar 19 16:21 libboost_filesystem-mt-1_42.so.1 -> libboost_filesystem-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 37 Mar 19 16:21 libboost_filesystem-mt-1_42.so.1.42 -> libboost_filesystem-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 84776 Mar 19 16:21 libboost_filesystem-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:20 libboost_iostreams-1_42.so -> libboost_iostreams-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:20 libboost_iostreams-1_42.so.1 -> libboost_iostreams-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:20 libboost_iostreams-1_42.so.1.42 -> libboost_iostreams-1_42.so.1.42.0
-rwxr-xr-x 1 root root 117656 Mar 19 16:20 libboost_iostreams-1_42.so.1.42.0
lrwxrwxrwx 1 root root 36 Mar 19 16:20 libboost_iostreams-mt-1_42.so -> libboost_iostreams-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 36 Mar 19 16:20 libboost_iostreams-mt-1_42.so.1 -> libboost_iostreams-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 36 Mar 19 16:20 libboost_iostreams-mt-1_42.so.1.42 -> libboost_iostreams-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 117656 Mar 19 16:20 libboost_iostreams-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 39 Mar 19 16:16 libboost_program_options-1_42.so -> libboost_program_options-1_42.so.1.42.0
lrwxrwxrwx 1 root root 39 Mar 19 16:16 libboost_program_options-1_42.so.1 -> libboost_program_options-1_42.so.1.42.0
lrwxrwxrwx 1 root root 39 Mar 19 16:16 libboost_program_options-1_42.so.1.42 -> libboost_program_options-1_42.so.1.42.0
-rwxr-xr-x 1 root root 373312 Mar 19 16:16 libboost_program_options-1_42.so.1.42.0
lrwxrwxrwx 1 root root 42 Mar 19 16:16 libboost_program_options-mt-1_42.so -> libboost_program_options-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 42 Mar 19 16:16 libboost_program_options-mt-1_42.so.1 -> libboost_program_options-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 42 Mar 19 16:16 libboost_program_options-mt-1_42.so.1.42 -> libboost_program_options-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 373312 Mar 19 16:16 libboost_program_options-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:18 libboost_python-1_42.so -> libboost_python-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:18 libboost_python-1_42.so.1 -> libboost_python-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:18 libboost_python-1_42.so.1.42 -> libboost_python-1_42.so.1.42.0
-rwxr-xr-x 1 root root 335760 Mar 19 16:18 libboost_python-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:18 libboost_python-mt-1_42.so -> libboost_python-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:18 libboost_python-mt-1_42.so.1 -> libboost_python-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:18 libboost_python-mt-1_42.so.1.42 -> libboost_python-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 335760 Mar 19 16:18 libboost_python-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 29 Mar 19 16:20 libboost_regex-1_42.so -> libboost_regex-1_42.so.1.42.0
lrwxrwxrwx 1 root root 29 Mar 19 16:20 libboost_regex-1_42.so.1 -> libboost_regex-1_42.so.1.42.0
lrwxrwxrwx 1 root root 29 Mar 19 16:20 libboost_regex-1_42.so.1.42 -> libboost_regex-1_42.so.1.42.0
-rwxr-xr-x 1 root root 922240 Mar 19 16:20 libboost_regex-1_42.so.1.42.0
lrwxrwxrwx 1 root root 32 Mar 19 16:20 libboost_regex-mt-1_42.so -> libboost_regex-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 32 Mar 19 16:20 libboost_regex-mt-1_42.so.1 -> libboost_regex-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 32 Mar 19 16:20 libboost_regex-mt-1_42.so.1.42 -> libboost_regex-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 922240 Mar 19 16:20 libboost_regex-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 31 Mar 19 16:17 libboost_signals-1_42.so -> libboost_signals-1_42.so.1.42.0
lrwxrwxrwx 1 root root 31 Mar 19 16:17 libboost_signals-1_42.so.1 -> libboost_signals-1_42.so.1.42.0
lrwxrwxrwx 1 root root 31 Mar 19 16:17 libboost_signals-1_42.so.1.42 -> libboost_signals-1_42.so.1.42.0
-rwxr-xr-x 1 root root 84576 Mar 19 16:17 libboost_signals-1_42.so.1.42.0
lrwxrwxrwx 1 root root 34 Mar 19 16:17 libboost_signals-mt-1_42.so -> libboost_signals-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 34 Mar 19 16:17 libboost_signals-mt-1_42.so.1 -> libboost_signals-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 34 Mar 19 16:17 libboost_signals-mt-1_42.so.1.42 -> libboost_signals-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 84576 Mar 19 16:17 libboost_signals-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:15 libboost_system-1_42.so -> libboost_system-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:15 libboost_system-1_42.so.1 -> libboost_system-1_42.so.1.42.0
lrwxrwxrwx 1 root root 30 Mar 19 16:15 libboost_system-1_42.so.1.42 -> libboost_system-1_42.so.1.42.0
-rwxr-xr-x 1 root root 14360 Mar 19 16:15 libboost_system-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:15 libboost_system-mt-1_42.so -> libboost_system-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:15 libboost_system-mt-1_42.so.1 -> libboost_system-mt-1_42.so.1.42.0
lrwxrwxrwx 1 root root 33 Mar 19 16:15 libboost_system-mt-1_42.so.1.42 -> libboost_system-mt-1_42.so.1.42.0
-rwxr-xr-x 1 root root 14360 Mar 19 16:15 libboost_system-mt-1_42.so.1.42.0 |
is it normal that there are broken links in /usr/lib/boost-1_42?
Code: | spectred@PC-SPECTRED /usr/lib/boost-1_42 $ ls -l
total 0
lrwxrwxrwx 1 root root 32 Mar 17 20:36 libboost_date_time-mt.so -> ../libboost_date_time-mt-1_42.so <- broken
lrwxrwxrwx 1 root root 29 Mar 17 20:36 libboost_date_time.so -> ../libboost_date_time-1_42.so <- broken
lrwxrwxrwx 1 root root 33 Mar 19 16:21 libboost_filesystem-mt.so -> ../libboost_filesystem-mt-1_42.so
lrwxrwxrwx 1 root root 30 Mar 19 16:21 libboost_filesystem.so -> ../libboost_filesystem-1_42.so
lrwxrwxrwx 1 root root 32 Mar 19 16:20 libboost_iostreams-mt.so -> ../libboost_iostreams-mt-1_42.so
lrwxrwxrwx 1 root root 29 Mar 19 16:20 libboost_iostreams.so -> ../libboost_iostreams-1_42.so
lrwxrwxrwx 1 root root 38 Mar 19 16:16 libboost_program_options-mt.so -> ../libboost_program_options-mt-1_42.so
lrwxrwxrwx 1 root root 35 Mar 19 16:16 libboost_program_options.so -> ../libboost_program_options-1_42.so
lrwxrwxrwx 1 root root 29 Mar 19 16:18 libboost_python-mt.so -> ../libboost_python-mt-1_42.so
lrwxrwxrwx 1 root root 26 Mar 19 16:18 libboost_python.so -> ../libboost_python-1_42.so
lrwxrwxrwx 1 root root 28 Mar 19 16:20 libboost_regex-mt.so -> ../libboost_regex-mt-1_42.so
lrwxrwxrwx 1 root root 25 Mar 19 16:20 libboost_regex.so -> ../libboost_regex-1_42.so
lrwxrwxrwx 1 root root 30 Mar 19 16:17 libboost_signals-mt.so -> ../libboost_signals-mt-1_42.so
lrwxrwxrwx 1 root root 27 Mar 19 16:17 libboost_signals.so -> ../libboost_signals-1_42.so
lrwxrwxrwx 1 root root 29 Mar 19 16:15 libboost_system-mt.so -> ../libboost_system-mt-1_42.so
lrwxrwxrwx 1 root root 26 Mar 19 16:15 libboost_system.so -> ../libboost_system-1_42.so
lrwxrwxrwx 1 root root 29 Mar 17 20:34 libboost_thread-mt.so -> ../libboost_thread-mt-1_42.so <- broken
lrwxrwxrwx 1 root root 26 Mar 17 20:34 libboost_thread.so -> ../libboost_thread-1_42.so <- broken |
boost has "date_time filesystem iostreams program_options python regex signals system thread" enabled and every "boost-"-package emerged without problems. |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Fri Mar 19, 2010 4:29 pm Post subject: |
|
|
wrt broken links, this helps to identify and fix for yourself.
in the end just remove what is not there.
Quote: | # equery belongs <file> | looks all fine then. _________________ hear hear |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Fri Mar 19, 2010 5:37 pm Post subject: |
|
|
geki wrote: | wrt broken links, this helps to identify and fix for yourself.
in the end just remove what is not there.
Quote: | # equery belongs <file> | looks all fine then. |
seems that I missed them when cleaning the old stuff.
to be completely safe I unmerged boost deleted the remaining links and reemerged boost.
the broken links are gone now but the problem persists.. |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Fri Mar 19, 2010 6:06 pm Post subject: |
|
|
well, I had to rip the boost check from cmake for mysql-connector-c++ since it just looks in default include path.
luckily that is the only cmake based package I use with boost.
I still wonder about the SLOTing of boost. but o well, that is another story filled with flamewars. so I shut up again.
as a hack one could do symlinks.
edit #1
and even better make boost-headers depend on eselect-boost and make it symlink the headers at least.
should help most configures. but then may conflict with packages in need of special version.
whatever way it just fails, fun ...
!!! warning !!! there may be not so serious comments included.
edit #2
so the only sane way I see
... would be to have the path '/usr/include/boost' inside the sandbox point to the wanted/required version of boost. and not take the path '/usr/include/boost' set by eselect. is that possible?! fun ...
why?
well, configure scripts just set the default include path and therefore get the eselected version and not the wanted/required version.
can you follow?
the complication of multiple installs where the general (configures) does not expect it.
so the user has to take care what he/she sets by eselect. _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sat Mar 20, 2010 11:29 am Post subject: |
|
|
well, the only sane and simple way to handle this mess is to remove the slotting of boost-headers. another way makes it hardly possible to depend on a specific version. eselect backfires merciless there.
the libraries may stay slotted since the boost-utils eclass detects the correct version from boost headers at build-time. ( function: add_boost_paths )
if you merged eselect-boost, remove it and ...
Quote: | rm /usr/include/boost | for that the eselect does not clean up after itself ...
this should cover the configures that just look into default include path. mysql-connector-c++ is happy now. openoffice will be happy either. so am I. *puh* _________________ hear hear |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Sun Mar 21, 2010 5:39 pm Post subject: |
|
|
May it be possible that "dev-libs/boost-headers:${SLOT}" in the boost depend is not valid anymore with the current boost-headers? |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sun Mar 21, 2010 10:32 pm Post subject: |
|
|
yes, fixed that. _________________ hear hear |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Sun Mar 21, 2010 10:39 pm Post subject: |
|
|
there are still some ebuilds like mkvtoolnix that fail to compile.
I don't know the initial cause for this but I can guess the problem.
configure tests with -lboost_system, ... if linking against boost works.
BOOST_LDFLAGS is set to '-L/usr/lib64' and BOOST_SYSTEM_LIB to '-lboost_system'.
the problem is that in lib64 only versioned libs are available and -lboost_... in combination with -L/usr/lib64 fails..
when I manually create unversioned links in /usr/lib64 to the versioned ones at least mkvtoolnix compiles fine. |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Mon Mar 22, 2010 10:32 am Post subject: |
|
|
you just have to use the utils eclass and fix the depend. first post has a description. _________________ hear hear |
|
Back to top |
|
|
SpectreDragon Tux's lil' helper
Joined: 22 Aug 2008 Posts: 92 Location: Germany
|
Posted: Mon Mar 22, 2010 1:43 pm Post subject: |
|
|
geki wrote: | you just have to use the utils eclass and fix the depend. first post has a description. |
oh sorry, it's hard to follow all those changes |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Mon Mar 22, 2010 3:36 pm Post subject: |
|
|
no need to be sorry.
and if you know what boost libraries are required, like regex for mkvtoolnix, you just need to add the utils eclass and its function to src_configure. that should suffice. _________________ hear hear |
|
Back to top |
|
|
one_and_only Apprentice
Joined: 13 May 2007 Posts: 250 Location: PL/Krakow
|
Posted: Tue Apr 13, 2010 9:13 am Post subject: |
|
|
Got problem with emerging boost-mpi;
Quote: |
>>> Unpacking source...
tar xjpf /var/tmp/portage/dev-libs/boost-mpi-1.42.0/distdir/boost_1_42_0.tar.bz2 --exclude=boost_1_42_0/boost --exclude=boost_1_42_0/libs
tar xjpf /var/tmp/portage/dev-libs/boost-mpi-1.42.0/distdir/boost_1_42_0.tar.bz2 boost_1_42_0/libs/mpi
>>> Source unpacked in /var/tmp/portage/dev-libs/boost-mpi-1.42.0/work
>>> Preparing source in /var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0 ...
* Applying remove-toolset-1.42.0.patch ... [ ok ]
* Applying skip-headers.diff ... [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0 ...
* Writing new user-config.jam
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0 ...
* Using the following command to build:
* bjam-1_42 -j4 -q -d+2 gentoorelease --with-mpi pch=off --user-config="/var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0/user-config.jam" --boost-build=/usr/share/boost-build-1_42 --prefix="/var/tmp/portage/dev-libs/boost-mpi-1.42.0/image//usr" --layout=versioned threading=single,multi link=shared runtime-link=shared
Building the Boost C++ Libraries.
After the build, the headers will be located at
/var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0
The libraries will be located at
/var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0/stage/lib
Use 'bjam install --prefix=<path>' if you wish to install headers and
libraries to a different location and remove the source tree.
error: Unable to find file or target named
error: '/var/tmp/portage/dev-libs/boost-mpi-1.42.0/work/boost_1_42_0/libs/serialization/build//boost_serialization'
error: referred from project at
error: 'libs/mpi/build'
* ERROR: dev-libs/boost-mpi-1.42.0 failed:
* building boost failed
|
Is this somehow connected with bug in boost-build http://article.gmane.org/gmane.comp.lib.boost.build/22119 ? |
|
Back to top |
|
|
Yamakuzure Advocate
Joined: 21 Jun 2006 Posts: 2285 Location: Adendorf, Germany
|
Posted: Tue Apr 13, 2010 10:18 am Post subject: Re: split build of boost.org libraries |
|
|
First of all: Great work, geki!
I have only one thing: geki wrote: | still, one useful library is program_options for its 'program option parser' & 'help message generator'.
you just do not write that on your own, do you? | Of course I do. Because boost is a too enlarged monster to install just for _that_ (which now comes to an end once enough of the right people are convinced that a split-packaged boost is an excellent idea!) _________________ Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Tue Apr 13, 2010 12:12 pm Post subject: |
|
|
one_and_only
going to fix, thanks for reporting!
Yamakuzure
o, boost has more features one does not want to miss. that was just one tiny bit and even only for that I would use it.
I just do not like to reinvent the wheel and do extra work which is already done and tested.
well, just my damned lazy pov. _________________ hear hear |
|
Back to top |
|
|
ComaWhite Tux's lil' helper
Joined: 07 Oct 2008 Posts: 125
|
Posted: Thu Apr 15, 2010 9:59 pm Post subject: |
|
|
please do not use crappy bjam, use the cmake version much better |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Thu Apr 15, 2010 10:14 pm Post subject: |
|
|
if that was up-to-date, its wiki states 1.41 as latest, whereas 1.43 is around the corner. _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Thu May 06, 2010 4:50 pm Post subject: |
|
|
1.43 bumped
- please report issues
have fun! _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sat Aug 28, 2010 4:01 pm Post subject: |
|
|
old hat for most, but some people might not know yet: bumped to 1.44 _________________ hear hear |
|
Back to top |
|
|
Yamakuzure Advocate
Joined: 21 Jun 2006 Posts: 2285 Location: Adendorf, Germany
|
Posted: Sun Sep 05, 2010 12:47 pm Post subject: |
|
|
Hi there!
I just added your overlay via layman and updated my eix cache. For your boost ebuilds eix displays the following (example): Code: | # eix boost-random
* dev-libs/boost-random [1]
Available versions:
((get_version_component_range 1-2)) ~1.42.0
(1.43) ~1.43.0!s
(1.44) ~1.44.0!s
{debug doc static-libs test threads tools}
Homepage: http://www.boost.org/
Description: Boost random Libraries for C++
[1] "geki-overlay" /var/lib/layman/openoffice-geki | Is the topmost slot intentional? _________________ Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sun Sep 05, 2010 1:48 pm Post subject: |
|
|
diff shows no change in ebuilds.
and eclass has this:
Quote: | eclass/boost.eclass:SLOT="$(get_version_component_range 1-2)" | no idea. _________________ hear hear |
|
Back to top |
|
|
|