Glen Barber wrote:
>> How about the ability to add new commands to "pkg"?
>> For example something like "pkg cutleaves" via plugins would be cool.
>
> I think 'pkg autoremove' already does this.
Does autoremove show you all the leaves and ask which ones you want
removed? I honestly don't know (an
Marin Atanasov Nikolov wrote:
> This is just to share with you that soon after the official 1.0
> release of pkgng we now have basic plugins support in pkgng's
> development branch.
> [...]
> It's not perfect or covering everything, but it will give you a quick
> start though :)
How about the abi
Devin Teske wrote:
>> "Toggle Startup Services" dialog shows sendmail_enable and
>> sendmail_msp_queue_enable variables, but doesn't seem to show
>> sendmail_submit_enable and sendmail_outbound_enable. Is this
>> by design?
>
> What does the following produce:
>
> service sendmail rcvar
>
Devin Teske wrote:
> If you have the time and/or energy, please test and report any issues that
> you experience.
"Toggle Startup Services" dialog shows sendmail_enable and
sendmail_msp_queue_enable variables, but doesn't seem to show
sendmail_submit_enable and sendmail_outbound_enable. Is this
b
Martin Wilke wrote:
> With the new mesa 8.0 release, accelerated support for a number of
> older graphic cards was dropped. At the moment we are not sure how to
> deal with that.We are thinking of just replacing mesa 7.11 with 8.0 or
> making a new flag like WITH_MESA= 7.11.2 / 8.0 in combination w
Baptiste Daroussin wrote:
> * pkg set -o oldorigin:neworigin allow the user to modify the origin of a
> packages (useful for MOVED)
Can such things be tracked automatically?
I.e. will "pkg upgrade" upgrade moved packages?
___
freebsd-current@freebsd.or
Chris Rees wrote:
> Any rc script that complains about an empty /var/run is buggy- it should be
> assumed that it will be emptied on boot.
Then why are there entries for /var/run/{named,ppp,wpa_supplicant}
in /etc/mtree/BSD.var.dist? Should they be removed?
___
Baptiste Daroussin wrote:
> when a package can be installed in both i386 and amd64
>
> and maybe in the Makefile:
>
> PKGARCH= i386 amd64
>
> or
>
> PKGARCH= x86:32 x86:64
Baptiste, if ABI/arch ids will leak out to port Makefiles (i.e. I will
need to care about them), then please lea
> Along with plain standard ones (plain world+kernel install of bare system)
> I'm working on creating specific images.
> Like with preset installed packages (kde-set, gnome-set, etc.), like with
> some patches (area51/kde-wip/kms) etc.
> So, I did not fully automated (yet) creating of this one ima
Antony Mawer wrote:
> Not sure if this is the right place to post it -- about 6 years ago I
> put together a module which displays an ASCII splash screen on boot
> (rather than the graphical splash_pcx and splash_bmp modules).
As a user, I think this is rather cool; at least it is more useful for
10 matches
Mail list logo
