TIA,
Matias
--
gento...@gentoo.org mailing list
> I'm trying to compile vim with +clipboard support. One can do this by
> passing --enable-clipboard to configure. There's no USE flag for this
> feature. After some research, I've learned that the way to do this is to
> configure the EXTRA_ECONF variable. Now the question is: is there a
> file to put these variables in? Something like /etc/portage/package.use
> but for econfs?
You can set variables for individual ebuilds using /etc/portage/bashrc.
save the attached file as /etc/portage/bashrc then do
mkdir -p /etc/portage/env.d/app-editors
echo >>/etc/portage/env.d/app-editors/vim 'EXTRA_ECONF="--enable-clipboard"'
You can use this to set variables, or override default settings, for any
package.
--
Neil Bothwick
The trouble with doing something right the first time is that nobody
appreciates how difficult it was.
You could try using /etc/portage/bashrc, see portage(5). Use at your own
risk.
Hope that helps,
Tom
--
Tom Martin, http://dev.gentoo.org/~slarti
AMD64, net-mail, shell-tools, vim, recruiters
Gentoo Linux
Ooh that's quite nifty. I'll have to write that one down. Thanks, Neil. :)
--Peter
--
gento...@gentoo.org mailing list
Oh, Neil, you're kidding, right? I'd had to use FEATURES="-nostrip" on
the command line for *ages* to get SDL to emerge unstripped so that it
would work with NWMovies (the hack that allows Neverwinter Nights to
play movies inside the game, like normal); the only reason I stopped was
because with the very most recent versions of SDL even that doesn't work
and I have to compile it manually after hacking one line in video.c.
But you're saying I could have just added echo >>
/etc/portage/env.d/media-libs/libsdl 'FEATURES="nostrip"' to
/etc/portage/bashrc and I would have been done, all those times-- could
have just emerged normally?
But man 5 portage doesn't say anything about /etc/portage/env.d, and it
doesn't say anything much about what precisely you can put in
/etc/portage/bashrc either:
SYNOPSIS
/etc/
make.globals
make.conf(5)
/etc/make.profile/
deprecated
make.defaults
packages
packages.build
package.provided
parent
use.defaults
use.mask
virtuals
/etc/portage/
bashrc
package.mask
package.unmask
package.keywords
package.use
mirrors
categories
/etc/portage/profile/
site-specific overrides of /etc/make.profile/
/usr/portage/profiles/
arch.list
categories
info_pkgs
info_vars
package.mask
profiles.desc
thirdpartymirrors
use.desc
use.local.desc
use.mask
/var/lib/portage/
world
(note no /etc/portage/env.d mentioned, so how would one know to create
it or that it would be recognized by Portage)
/etc/portage/
bashrc If needed, this file can be used to set up a
special environment for ebuilds, different from the
standard root environment. The syntax is the same
as for any other bash script.
(this says almost nothing, frankly, unless you are very familiar with
the 'standard root environment for ebuilds', and again, doesn't say
anything about which particular features of this enviroment may be
varied by this file, or if any of them may not be, in true 'not yet
implemented' fashion).
But then again, I restrict myself to the last stable version of Portage:
* sys-apps/portage
Available versions: 2.0.51.22-r3 ~2.0.53_rc5 [M]2.1.0_alpha20050718
Installed: 2.0.51.22-r3
Is it possible that the man page is updated in the unstable versions, or
that this is implemented in the unstable versions only, or are you just
very clever to have figured this all out :-) ?
Holly
--
gento...@gentoo.org mailing list
The /etc/portage/bashrc file can be (ab)used to do all kinds of things
with the emerge command. Because the use of it can allow a user to not
only shoot themselves in the foot, but blow up the entire system, it
isn't heavily documented.
Basically, it is one of those things that if you don't know what you are
doing, then either stay away from it or have extensive backups of your
system.
Finally, this doesn't mean that you shouldn't use Neil's suggestion.
Just make sure that you are comfortable with the supplied bashrc before
implementing.
Regards,
Paul
--
gento...@gentoo.org mailing list
Incorrect. USE="vim-with-x".
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
> But you're saying I could have just added echo >>
> /etc/portage/env.d/media-libs/libsdl 'FEATURES="nostrip"' to
> /etc/portage/bashrc and I would have been done, all those times-- could
> have just emerged normally?
No, you put the settings in /etc/portage/env.d/cate-gory/package. Use the
attached script for bashrc.
> But man 5 portage doesn't say anything about /etc/portage/env.d,
It wouldn't, that directory is used by that particular bashrc script.
bashrc is run by ebuild at various stages of the process.
--
Neil Bothwick
If bankers can count, how come they have eight windows and only four
tellers?
> Finally, this doesn't mean that you shouldn't use Neil's suggestion.
> Just make sure that you are comfortable with the supplied bashrc before
> implementing.
And don't blame me if it does go BOOM! :)
--
Neil Bothwick
"Mr. Worf, scan that ship." "Aye Captain. 300 dpi?"
Nice! thanks so much; maybe I'll try this next time. It seems that this
time I've missed some doc:
Nicer! So this is what vim-with-x stand for! I saw the flag, but thought
that it would pull down gvim, which I already have in my world.
Now: this pops up a second question: where can we see the exact efect of USE
flags on packages? For instance: what other features 'vim-with-x' will
enable?
USE flag descriptions can be found in /usr/portage/profiles. There are
two files:
/usr/portage/profiles/use.desc (for global USE flags), and
/usr/portage/profiles/use.local.desc (for local USE flags relevant to
individual packages).
You can of course search/grep normally through these files, but I find
it easier to nick an alias that someone on the list provided, and add it
to ~/.bashrc:
alias useflag='grep /usr/portage/profiles/use.*desc -e'
which enables me to do this (after re-sourcing ~/.bashrc, which I also
have an alias to do :-) ):
di 10/18/05 15:39
~
motub-> useflag vim-with-x
/usr/portage/profiles/use.local.desc:app-editors/vim:vim-with-x -
Linking console vim against X11 libraries to enable title and clipboard
features in xterm
And now I know what it does, instead of guessing ;-) .
Hope this helps
Aha! Now it seems that I have an old (or not so accurate)
/usr/portage/profiles/use.local.desc:
/usr/portage/profiles/use.local.desc:app-editors/vim:vim-with-x -
Enables linking the console vim against X libs to enable some features
in xterms
This is why I neglected to see that clipboard and vim-with-x were
related. But what I find confusing now is why I have this difference.
How does one update the use.local.desc file? It seems not to belong to
any package
(tried "equery belongs /usr/portage/profiles/use.local.desc"
and didn't get any answer).
MatÃas
--
gento...@gentoo.org mailing list
emerge sync
You're not out of sync, Holly is, possibly an upstream sync issue.
> This is why I neglected to see that clipboard and vim-with-x were
> related. But what I find confusing now is why I have this difference.
> How does one update the use.local.desc file? It seems not to belong to
> any package
> (tried "equery belongs /usr/portage/profiles/use.local.desc"
> and didn't get any answer).
This file is resynced when you 'emerge --sync'; it is not owned by a package
in portage. If you look at the timestamp of the file it should match the
date of your last sync.
For Holly's case, I'm wondering if she's syncing against a system that doesn't
mirror that file from upstream? Just a guess.
--
gento...@gentoo.org mailing list
Everything under $PORTDIR (usually /usr/portage) except for distfiles
gets updated by "emerge --sync".
Cheers,
Renat
--
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
(Einstein)
????!!!! I esync every night at 3am CET. How can I be out of sync? And,
if Matias somehow synced more recently than I did, how can his sync
result in a *less* informative description than the allegedly older one
(mine) ?
> This file is resynced when you 'emerge --sync'; it is not owned by a
> package in portage. If you look at the timestamp of the file it
> should match the date of your last sync.
la /usr/portage/profiles
totaal 261
drwxr-xr-x 15 root root 720 okt 18 02:36 .
drwxr-xr-x 152 root root 4496 okt 18 02:36 ..
-rw-r--r-- 1 root root 97 aug 14 13:35 arch.list
drwxr-xr-x 2 root root 184 okt 16 11:05 base
-rw-r--r-- 1 root root 1541 sep 4 16:36 categories
drwxr-xr-x 3 root root 72 apr 25 05:37 commercial
drwxr-xr-x 3 root root 72 aug 26 2004 default-bsd
drwxr-xr-x 4 root root 288 okt 6 05:38 default-darwin
drwxr-xr-x 15 root root 552 okt 7 01:06 default-linux
drwxr-xr-x 3 root root 128 feb 7 2005 default-macos
drwxr-xr-x 2 root root 152 okt 18 02:36 embedded
drwxr-xr-x 6 root root 304 okt 6 05:38 hardened
-rw-r--r-- 1 root root 257 apr 28 07:07 info_pkgs
-rw-r--r-- 1 root root 370 apr 11 2005 info_vars
-rw-r--r-- 1 root root 7270 nov 8 2002 lang.desc
drwxr-xr-x 11 root root 288 aug 14 00:05 obsolete
-rw-r--r-- 1 root root 51812 okt 18 00:05 package.mask
-rw-r--r-- 1 root root 828 sep 5 19:35 profiles.desc
drwxr-xr-x 4 root root 288 okt 14 01:05 selinux
-rw-r--r-- 1 root root 62518 okt 11 13:35 thirdpartymirrors
drwxr-xr-x 7 root root 392 okt 18 02:36 uclibc
drwxr-xr-x 2 root root 384 okt 17 04:08 updates
-rw-r--r-- 1 root root 20490 okt 17 02:06 use.desc
-rw-r--r-- 1 root root 89205 okt 18 02:06 use.local.desc
drwxr-xr-x 3 root root 296 sep 26 12:35 vserver
So no, use.local.desc is at least current, and use.desc has apparently
not changed for one day longer.
>
> For Holly's case, I'm wondering if she's syncing against a system
> that doesn't mirror that file from upstream? Just a guess.
I sync against the Netherlands rsync pool,
SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage".
I suppose what you say is possible, but does not seem to be the case.
I figured you sync'd daily Holly; I wouldn't have expected any less. ;-)
The question is, however, if you and I both sync daily and, although file
times suggest they have been updated, but the file contents are different,
where would the problem lie?
The only guess I could come up with is the upstream mirror. I sync against
http://gentoo.osuosl.org/, and you're syncing against the netherlands pool.
Either one themselves could be sync'd against another mirror which is sync'd
against another mirror...
Somewhere along the line I'm guessing that perhaps this particular file is not
fetched/updated for some reason which would leave one of us with an outdated
copy.
I know mine comes out of CVS with the header
$Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1502 2005/10/18
00:03:00 vapier Exp $, so I'm guessing that I have the later file.
--
gento...@gentoo.org mailing list
app-editors/vim:vim-with-x - Linking console vim against X11 libraries
to enable title and clipboard features in xterm
spider@Darkmere> head -n 4 use.local.desc |tail -n 2
# $Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1505
2005/10/18 20:18:45 agriffis Exp $
//Spider
--
begin .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end
So does mine:
# $Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1502
2005/10/18 00:03:00 vapier Exp $
are you saying that this line
app-editors/vim:vim-with-x - Linking console vim against X11 libraries
to enable title and clipboard features in xterm
is not the same on your file, despite the identical header?
I mustbe getting old or something. I swear when I looked at it before it
matched the other guys and not yours. Now mine matches yours. I need to
start drinking ;-)
--
gento...@gentoo.org mailing list
Wheee, another person successfully confused by sneakily changing stuff
in response to mailing list questions and not bothering to announce the
fact. You're all crazy, anyway. There's no "ing" in the description.
OK, now I re "emerge --sync"d, and I got the new description. My older
description was from
# $Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1500 2005/10/16 21:25:13 brix Exp $
I've found some mental peace state now :)
Thanks to all of you!