I typically do Everything installs on my personal workstations. Simplifies life greatly.
However, it would be nice if there were:
"Everything ONLY English" (ie, no foreign language support)
"Everything NO Development"
Comments?
On Thu, 2003-07-24 at 16:22, Dax Kelson wrote:
I typically do Everything installs on my personal workstations. Simplifies life greatly.
However, it would be nice if there were:
"Everything ONLY English" (ie, no foreign language support)
"Everything NO Development"
Comments?
Definitely dont' think that's a good idea. It solves perhaps your problem, but I'm there are many users who have other specific package sets they'd love install options for too. What we'd end up with is an Everything menu with tons of semi-Everythings, covering everything imaginable, even tho they aren't Everything. ~,^
Seriously, it's not that much work to just select the package groups. If you do find yourself spending too much time on it, quit reinstalling your machines so often. ;-) Or just use Kickstart.
-- Rhl-devel-list mailing list Rhl-devel-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-devel-list
On Thu, 2003-07-24 at 14:29, Sean Middleditch wrote:
On Thu, 2003-07-24 at 16:22, Dax Kelson wrote:
I typically do Everything installs on my personal workstations. Simplifies life greatly.
However, it would be nice if there were:
"Everything ONLY English" (ie, no foreign language support)
"Everything NO Development"
Comments?
Seriously, it's not that much work to just select the package groups.
If you go through and click every checkbox available to you in the package groups, what you end up with is vastly different then an Everything install.
At the same time, Everything install can be too much. There is no middle ground.
Personally, I would install my machines with "Everything ONLY English".
On Thu, 2003-07-24 at 16:39, Dax Kelson wrote:
Personally, I would install my machines with "Everything ONLY English".
Again, then, just use Kickstart.
No sense in adding 10 billion install options for each and every unique Redhat user when a good solution exists for users to make their own install sets. ;-)
-- Rhl-devel-list mailing list Rhl-devel-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-devel-list
On Thu, 24 Jul 2003, Scott Becker wrote:
How about:
a "Everything" b "Everything in the selected language"
or making Everything do just packages for the selected language and then to get **everything** you just select all languages
packages don't provide any indication of "language".
a "Everything" b "Everything in the selected language"
or making Everything do just packages for the selected language and then to get **everything** you just select all languages
packages don't provide any indication of "language".
Apparently you aren't familiar with the %lang macro?
-Chuck
On Fri, 25 Jul 2003, Chuck Wolber wrote:
a "Everything" b "Everything in the selected language"
or making Everything do just packages for the selected language and then to get **everything** you just select all languages
packages don't provide any indication of "language".
Apparently you aren't familiar with the %lang macro?
Thanks for the pointer; I wasn't.
But the problem in this context is more with how you export that information out of the packages, so that you can say to give a toggle to the installer that you want all packages with %lang FOO or %lang unspecified (implying english).
I'm not sure how this is doable.
Apparently you aren't familiar with the %lang macro?
Thanks for the pointer; I wasn't.
But the problem in this context is more with how you export that information out of the packages, so that you can say to give a toggle to the installer that you want all packages with %lang FOO or %lang unspecified (implying english).
I'm not familiar with the commandline options, but IIRC you can tease out %lang information from a package using the rpm command. I suspect that it may require some basic grep'ing and whatnot.
-Chuck
The rpm command you need is rpm -q --qf %{FILELANGS} <package>.
On my severn system:
hbo@mycop|1016> rpm -q --qf %{FILELANGS} kde-i18n-British en_GB hbo@mycop|1017>
Whereas:
hbo@mycop|1017> rpm -q --qf %{FILELANGS} openssh hbo@mycop|1018>
So, no output for packages without "FILELANGS". I haven't looked into whether FILELANGS corresponds to to %lang, but I assume it does.
On Thu, 2003-08-07 at 01:32, Chuck Wolber wrote:
Apparently you aren't familiar with the %lang macro?
Thanks for the pointer; I wasn't.
But the problem in this context is more with how you export that information out of the packages, so that you can say to give a toggle to the installer that you want all packages with %lang FOO or %lang unspecified (implying english).
I'm not familiar with the commandline options, but IIRC you can tease out %lang information from a package using the rpm command. I suspect that it may require some basic grep'ing and whatnot.
-Chuck
On Thu, 2003-07-24 at 23:57, Pekka Savola wrote:
On Thu, 24 Jul 2003, Scott Becker wrote:
How about:
a "Everything" b "Everything in the selected language"
or making Everything do just packages for the selected language and then to get **everything** you just select all languages
packages don't provide any indication of "language".
I thought that was handled in the 'comps' file of the installer, otherwise what would the "Language Selection" page be for?
On Thu, 2003-07-24 at 16:29, Sean Middleditch wrote:
On Thu, 2003-07-24 at 16:22, Dax Kelson wrote:
I typically do Everything installs on my personal workstations. Simplifies life greatly.
However, it would be nice if there were:
"Everything ONLY English" (ie, no foreign language support)
"Everything NO Development"
Comments?
Definitely dont' think that's a good idea. It solves perhaps your problem, but I'm there are many users who have other specific package sets they'd love install options for too. What we'd end up with is an Everything menu with tons of semi-Everythings, covering everything imaginable, even tho they aren't Everything. ~,^
Seriously, it's not that much work to just select the package groups. If you do find yourself spending too much time on it, quit reinstalling your machines so often. ;-) Or just use Kickstart.
I think more people speak other languages than do speak American English, but I understand where you are going with the original suggestion. I sort of expanded on that idea as I personally think it's a good one, and filed this bugzilla report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=100888
You can read my suggestion there, but I can't say how much traction it will get for this release. It's more than likely too late for now.
On Thu, 2003-07-24 at 16:22, Dax Kelson wrote:
"Everything ONLY English" (ie, no foreign language support)
This really sucks from a user point of view. I'd be really curious to see what you define as foreign language support. Where do you draw the line? Translations, fonts, input methods, programs that are useful mainly because they support specific locales better?
Everything except some stuff has always seemed like a silly thing to me because everybody is going to have a different idea of what "some stuff" is for them.
Jeremy
On Jul 24, 2003, Jeremy Katz katzj@redhat.com wrote:
Everything except some stuff has always seemed like a silly thing to me because everybody is going to have a different idea of what "some stuff" is for them.
How about the following new categories (we can always work out what to place on each of them later):
- Nearly everything
- Pretty much everything
- Everything I might want to use
- Everything
- Everything, really (currently known as everything)
:-D
/me runs
-
Alexandre Oliva -
Chris Kloiber -
Chuck Wolber -
Dax Kelson -
Howard Owen -
Jeremy Katz -
Pekka Savola -
Scott Becker -
Sean Middleditch