Re: Utility for safe updating of ports in base system
On Fri, 21 Mar 2008 14:35:00 +0100 Nikola Lečić <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, 21 Mar 2008 00:49:05 +0100 > Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > In the past we've even talked about how to move all of pkg_* out of > > src and into ports, i.e. the opposite case. > > A propos (non-)removing pkg_* into the ports, what do you people think > of introducing bin-install ports make target (similar to what pkgsrc > has)? Besides, bin[-install]-fetch[-recursive] come to mind as well. > IMHO, this would have nice pedagogical and heuristic effect since it > could > > 1) resolve eternal users' confusion on what is the "difference between >ports and packages" and "between 'make install' and 'pkg_add'": it's >different if a package is actually installed by e,g. > cd /usr/ports/lang/python ; make [BIN_PKGSITES=...] bin-install > > 2) parallelise binary-install/compiling/local-package-building logics; > > 3) simplify things since it would cut proliferation of similar >command-line options and utilities/methods that do the same thing. > > Best regards. > - -- > Nikola Lečić = Никола Лечић > fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B I like the 'make update' target as implemented in OpenBSD. Its then very convenient to update a port when binary update is not an option. my 2 cents, - Etienne ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail
Hello, sorry once again for the delay. I have reviewed your patch and inserted it into portmgr's approval queue during the ports freeze. -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgpIieL7A2IFE.pgp Description: PGP signature
Fwd: Re: Incorrect commandline history with bash
Individual did not CC the mailing list on his response.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
- Forwarded message from manish jain <[EMAIL PROTECTED]> -
> From: manish jain <[EMAIL PROTECTED]>
> To: Jeremy Chadwick <[EMAIL PROTECTED]>
> Date: Mon, 22 Sep 2008 01:54:46 +0530
> Subject: Re: Incorrect commandline history with bash
>
> Thanks Jeremy. Sourcing .bash_profile from .bashrc solved the problem. For
> some reason, sourcing .bashrc from .bash_profile worked equally well with
> the version of Linux I was previously using.
>
> Regards
> Manish Jain
>
>
>
> On 9/21/08, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> >
> > On Sat, Sep 20, 2008 at 11:18:34PM +0530, manish jain wrote:
> > > I just migrated from Linux and I am now using FreeBSD 6.3. My keyboard
> > > layout is US-ISO and my TERM is con25. I am using bash#3 as my login
> > shell.
> > > (I installed the bash package from the distribution media, not from
> > > /usr/ports).
> > >
> > > The problem is that bash does not remember my commands correctly. Almost
> > all
> > > commands I enter in a login session are forgotten in the next session.
> > Using
> > > the Up and Down arrow keys navigates a mangled and incomlete command
> > > history. Even using Ctrl-r for a reverse find almost never fetches a
> > command
> > > I had actually typed in previously.
> > >
> > > The following are the contents of my .bash_profile and .bashrc:
> > >
> > > #.bash_profile :
> > > [ -f ~/.bashrc ] && source ~/.bashrc
> > > #end-of-file
> >
> > You have this backwards. ~/.bashrc should contain something like this:
> >
> > if [ -f "${HOME}/.bash_profile" ]
> > then
> > source "${HOME}/.bash_profile"
> > fi
> >
> > And all of your applicable environment settings should go in
> > .bash_profile. This probably won't solve your problem, but I thought
> > I'd point it out.
> >
> > > #.bashrc :
> > > export HISTFILESIZE=200
> > > shopt -s cmdhist
> > > shopt -s histappend
> > > #end-of-file
> >
> > I set none of these things (though I do use export HISTTIMEFORMAT="%T "
> > but that should not affect your problem) and my .bash_history always
> > contains commands from past sessions, including timestamps too.
> >
> > My options are defaults:
> >
> > $ shopt | egrep 'cmdhist|histappend'
> > cmdhist on
> > histappend off
> >
> > Can you please try pkg_delete'ing the bash you installed from the
> > installation media, and instead update your ports tree via csup (not
> > cvsup) and then build/install bash from /usr/ports/shells/bash?
> >
> > Finally, please do not cross-post to multiple lists. It's shunned upon,
> > and generally pointless as not everyone is subscribed to both lists.
> > I've removed [EMAIL PROTECTED], as this could be a ports
> > issue rather than a generic question.
> >
> > --
> > | Jeremy Chadwickjdc at parodius.com |
> > | Parodius Networking http://www.parodius.com/ |
> > | UNIX Systems Administrator Mountain View, CA, USA |
> > | Making life hard for others since 1977. PGP: 4BD6C0CB |
> >
> >
- End forwarded message -
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect commandline history with bash
On Sep 21, 2008, at 2:52 PM, Jeremy Chadwick wrote:
The following are the contents of my .bash_profile and .bashrc:
#.bash_profile :
[ -f ~/.bashrc ] && source ~/.bashrc
#end-of-file
You have this backwards. ~/.bashrc should contain something like
this:
if [ -f "${HOME}/.bash_profile" ]
then
source "${HOME}/.bash_profile"
fi
Jeremy, I'm not sure what version of FreeBSD you are using but I'd
like to point out that in 6.2 and 6.3-REL his version is correct and
yours will not work.
.bashrc is not sourced on login on any of my hosts. I have ".
~/.bashrc" in my .bash_profile. And I just commented it out,
and .bash_profile environment was set up, and the stuff in .bashrc was
not.
Is this perhaps an X versus SSH login sort of thing? I don't know.
We have no X environment, this is entirely logging in via SSH.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: Re: Incorrect commandline history with bash
At 2:52 PM -0700 9/21/08, Jeremy Chadwick wrote: Individual did not CC the mailing list on his response. - Forwarded message from manish jain <[EMAIL PROTECTED]> - > > Thanks Jeremy. Sourcing .bash_profile from .bashrc solved the > problem. For some reason, sourcing .bashrc from .bash_profile > worked equally well with the version of Linux I was previously > using. > Regards Manish Jain -end message from manish jain <[EMAIL PROTECTED]> - I do not understand how that makes any difference. He had all his commands in .bashrc, and sourced it from .bash_profile. If he moves all his commands to .bash_profile, and then sources that from his .bashrc, then isn't the result exactly the same? Either way, all commands should be executed no matter how bash starts up. I only mention this because my .bash_profile sources my .bashrc, and has done so on many different platforms for the past 18 years, and I've never had a problem with it. Although in my case it checks for and sources $HOME/.bashrc while he was using ~/.bashrc. Not only my .bash_profile, but every .bash_profile and .bashrc at RPI was setup this way. Tens of thousands of users, and I've never heard of anyone who had a problem with it. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect commandline history with bash
On Sun, Sep 21, 2008 at 03:54:12PM -0700, Jo Rhett wrote:
>
> On Sep 21, 2008, at 2:52 PM, Jeremy Chadwick wrote:
>>> The following are the contents of my .bash_profile and .bashrc:
>>>
>>> #.bash_profile :
>>> [ -f ~/.bashrc ] && source ~/.bashrc
>>> #end-of-file
>>
>> You have this backwards. ~/.bashrc should contain something like
>> this:
>>
>> if [ -f "${HOME}/.bash_profile" ]
>> then
>> source "${HOME}/.bash_profile"
>> fi
>
> Jeremy, I'm not sure what version of FreeBSD you are using but I'd like
> to point out that in 6.2 and 6.3-REL his version is correct and yours
> will not work.
That's funny, because mine does work. I spent quite a lot of time
looking at the bash man page over the years to determine how to properly
meet said needs. I use the exact same setup on Solaris 7/8/9/10 (bash
v2) and FreeBSD 4/5/6/7/8 (bash v3), and it works exactly how the man
page describes.
> .bashrc is not sourced on login on any of my hosts. I have ".
> ~/.bashrc" in my .bash_profile. And I just commented it out, and
> .bash_profile environment was set up, and the stuff in .bashrc was not.
Everyone lecturing me needs to read, slowly, the INVOCATION part of the
bash man page. The method I described above should become apparent
afterwards.
> Is this perhaps an X versus SSH login sort of thing? I don't know. We
> have no X environment, this is entirely logging in via SSH.
No, I do not use X anywhere. The OP may be using it.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: Re: Incorrect commandline history with bash
On Sun, Sep 21, 2008 at 06:45:22PM -0400, Garance A Drosihn wrote: > At 2:52 PM -0700 9/21/08, Jeremy Chadwick wrote: >> >> Individual did not CC the mailing list on his response. >> >> - Forwarded message from manish jain <[EMAIL PROTECTED]> - >> > >> > Thanks Jeremy. Sourcing .bash_profile from .bashrc solved the >> > problem. For some reason, sourcing .bashrc from .bash_profile >> > worked equally well with the version of Linux I was previously >> > using. >> > >>> Regards >>> Manish Jain >> -end message from manish jain <[EMAIL PROTECTED]> - > > I do not understand how that makes any difference. He had all his > commands in .bashrc, and sourced it from .bash_profile. If he > moves all his commands to .bash_profile, and then sources that > from his .bashrc, then isn't the result exactly the same? Either > way, all commands should be executed no matter how bash starts up. The INVOCATION section of the bash man page goes over the subtle differences. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect commandline history with bash
At 5:28 PM -0700 9/21/08, Jeremy Chadwick wrote: On Sun, Sep 21, 2008 at 06:45:22PM -0400, Garance A Drosihn wrote: > I do not understand how that makes any difference. He had all his commands in .bashrc, and sourced it from .bash_profile. If he moves all his commands to .bash_profile, and then sources that from his .bashrc, then isn't the result exactly the same? Either way, all commands should be executed no matter how bash starts up. The INVOCATION section of the bash man page goes over the subtle differences. Okay, I've re-read it, and I'm still missing what the difference would be. I'm not arguing that you're wrong, I'm just saying that I don't understand it. Apparently your advice did help the person with the original problem, but I'm still sitting here with literally tens of thousands of RPI users who did it "the wrong way", and not one of them has ever reported a problem due to that. Now, most of those people have never used FreeBSD, but I've used this same setup on freebsd for at least 13 years, and have never seen a problem. Given: a) .bashrc sources .bash_profile orb) .bash_profile sources .bashrc In both cases, both .bashrc and .bash_profile will exist. So, any decision that bash makes based on the *existence* of either file should be the same. In both cases, both files exist. If bash picks one file to source, that file will either contain the commands to execute, or it will source the other file which contains those very same commands. I don't see how that could possibly make any difference. Obviously I'm then at a loss to explain how the problem went away for the original user. All I can guess is that maybe one of the files was permitted wrong, and he happened to fix that while moving the files around. I admit that doesn't seem likely, but I just cannot see how your advice managed to fix his problem. Sign me: Confused in Troy... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
print/acroread8
Hello, # uname -a FreeBSD 7.1-PRERELEASE #0: Sun Sep 21 13:28:51 EST 2008 I just installed print/acroread8 from a ports tree that is about 1-2 days old (depending on your time zone). The plugin for firefox (mozilla) was installed to: /root/.mozilla/plugins/nppdf.so When I did: nsplugginwrapper -v -a -i it found the plugin, and: nsplugginwrapper -l lists it as installed, but firefox doesnt load it. So, I removed the plugin with: nspluginwrapper -r /root/.mozilla/plugins/npwrapper.nppdf.so then, moved the file nppdf.so into /usr/X11R6/lib/browser_plugins and then, reinstalled it from the new location with: nsplugginwrapper -v -a -i Now firefox loads the plugin and it all works as expected. I dont know if this is a packaging problem with acroread8, ie maybe it should drop the file nppdf.so into /usr/X11R6/lib/browser_plugins instead of /root/.mozilla/plugins - - - or maybe this is a problem with the wrapper not setting up the plugin properly. Anyway, this was the problem I encountered, and how to fix it manually in case anyone else is seeing this. Cheers, Tim. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
