Am 24.04.2013 13:44, schrieb Chris Rees:
On 24 Apr 2013 05:36, "Justin Edward Muniz" <justin.mu...@maine.edu>
wrote:
Justin I say stick to FreeBSD-update . My reason is, as Pkgng
becomes
more popular , a front end for ports will be less useful as binary
packages
become more popular . Kports is a monster program , you should set a
reasonable goal ,and target dates; which may be hard with a cleanup
project
. Also a update notifier for kde that handles FreeBSD update would
be
very useful .
My 2cents .
---
Mark saad | mark.s...@longcount.org
Thank you very much Mark,
I was definitely hoping to get community feedback on this, and I
value
you voicing your opinion. I agree that kports is a mammoth, and also
that
a
system updater GUI should have a way to notify the user of new
updates.
Any other perspectives are welcome, as well as support for a
freebsd-update approach. I am working to refine my proposal, which as
you've pointed out is very important. Eventually I would like to help
in
all three mentioned areas, but for now I must focus on one
application.
Does anyone think that a custom kernel configuration and management
GUI
utility would be desirable?
I will shape my goals to meet the needs of the community.
Our kernel is actually very easy to configure, so I'm not convinced
that
it's needed; you may be thinking of Linux's menuconfig, but I think
that is
because of the complexity.
It _is_ easy. But having a nice graphical tool which draws a pretty
table of
GENERIC and NOTES together with useful information about the possible
options
and devices would be a handy thing to have IMHO.
Let's make FreeBSD userfriendly :-)
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
