Can I install gnome from my 10.0 disk into 10.2?

And if so, (using pkgtool), what should I not install to avoid conflicts with whatever 10.2 installed? Or, if I install everything in the gnome folder, what should I reinstall from the 10.2 disc to avoid conflicts?

I know the second part may be a long process to explain.

you can...i did...i installed gnome from my 10.1 disk actually. i just cd'd into the gnome directory and ran "installpkg *.tgz" and it installed gnome, with no interference to any other programs. i run slack current, and use slackpkg to keep current, so sometimes, it will offer up some libraries and stuf to update that refer to gnome. i install them, and have never had a problem.

Kewl...will try the installpkg *.tgz

Just thought I'd play with gnome for awhile

linuce vanila gnome was very good, have a try(if u r going to use old gnome)that wont change any files

No thanks. gnome from 10.0 works fine, it's a known quantity, and used to be shipped with Slackware, so I know the packages are good, and don't have to worry about it.

I have a real aversion to compiling and slapping new stuff into my boxes without knowing exactly what I'm getting. Dropline Gnome is a stellar example of what NOT to install. Changes too much stuff you don't know about.

Actually, rkrishna is right. Linuce's Gnome is a straight up vanilla Gnome for Slackware that makes NO changes to your system what-so-ever. In fact it was 10x better than what Pat cranked out. Seriously. The guy is really anal and neat with his packages just like Slackware only he went the extra mile when building Gnome... And it shows.

Whatever happened to Linuce anyway? Haven't heard anything about him AND all his gnome stuff is gone from his server anyway so I guess this reply is moot.

yes jong357, me too missed him, he is noteven appearing in, posting replys too. i think 2.10.1 was his latest. no way so i use freerock gnme now
regards

It's only stuff you don't know about if you have problems reading above a sixth-grade level or haven't actually bothered to look.

We've always been very, very clear about what little we change and why we change it.

Shadow/login gets changed out to include a smidgen of PAM so that users no longer have to add their accounts permanently to the audio/cdrom groups just to be able to play sounds and mount media. (A whole RAFT of support questions go away from this alone. Has anyone had to add themselves to these groups with Dropline installed? No.) Security-concious users should have serious misgivings about assigning permanent ownership of console devices to accounts that may or may not be logged in from the console at that moment. Yes, I fully agree that PAM is a @#@% to deal with, but the users *don't* have to deal with it. It's preconfigured to "just work". (Nor are we deploying any of the other network-auth modules that people might hurt themselves with, so don't even try to bring that tired argument about the past security issues with those.)

X gets changed out to make a slight packaging reorg (i.e., freetype being kept external so an update to it doesn't require replacing the ENTIRE X package) and for the sake of efficiency, and to make sure people don't send us bug reports because they've installed only _half_ of Pat's X or equally silly things. It also ensures we can make minor appearance tweaks (like why you no longer have to put up with the basic/ugly X cursors) without stomping all over files in other, non-Dropline packages--which would be wrong, wrong, wrong.

I'm sticking to my point: I will never install Dropline Gnome again because of the things it changes, such as conf files, rc.* files, that it has NO BUSINESS messing with.

I have 1 question for everybody:

Has anyone sucessfully/easily uninstalled Dropline?
I mean, completely, without having to reconfigure many, many files?

Installing the old gnome from 10.0 was as easy as running pkgtool.
Uninstalling is as easy as running pkgtool.

Try that with dropline

Bet you "Didn't" know that udev is "Broke" per pats choice
in his "Good" udev pack did ya? Of course you did, you "Know"
that because it came with slackware it must be "Good"

Blah... whatever man, that was about the most ignorant statement
I have heard in awhile now. I've used dropline for a great while
now and it has "NEVER" busted my slackware install. Let me repeat,
"NEVER" busted my slackbox. You trolls crack me up when you con-
tinue to make these claims without any basis behind them. Some
guy back in the day had a bad install and talked trash about
dropline and it somehow stuck. I'd be hard pressed to say that
I can almost guarantee that 90% of the idiots out there that trash
dropline-gnome haven't ever even tried it just because they heard
from the slack zealots that it's bad for your system. Well I have
news for ya man, Most of the packs that it does replace are either
"Fixed" rebuilds or recent updates for gnome to function the way
it should. I would for once like to see one of you dlg bashers
actually post some legitimate reasons as to why you think dropline
breaks your system and that doesn't mean to post some stupid pam
crap that you and I both know is total B.S. Just because Pat is
stuck back in the 70's don't mean you need to be also.

p.s. Using Freerock as an example will not fly either. Although
I think it's a rather nice option for Slack, and the devs have
done a nice job with it, but it still lacks some functionality
of a full gnome desktop because it cators to the Slack zealots
and needs to build against Pats broken stuff so you will all be
happy. Oh by the way, Just to let you know, I've seen on many
occasions the freerock devs working with dlg devs to get problems
solved. Guess you wont be using that anymore now either will ya. :P

'Broke' because it did not work w/the Slack base kernel. But works fine on my system.
Tried it. It took over too much, changed too many conf files, and couldn't get rid of it. I ended up pulling a Windows and a format/reinstall.


***EDIT***

I'm sure dropline is fine for most. Just not for me.
If I wanted a Windows install that changes files without rhyme or reason, I'll go back to XP.
My system is MINE. Not droplines to "change security settings", or "fonts", or "cursors". If I want them changed, I will do it, not some wild eyed program doing it "for me". Windows did that enough for me.

Well first off, If you had to do a complete reinstall because of
a few config files then you shouldn't be messing with config files
in the first place. It don't take a rocket scientist to figure out
what has been changed and what hasn't. Removal of Dlg is rather
simple if you have somewhat of a clue as to what you are doing.

As far as "fonts", "cursors", and "security settings", What in
gods name are you talking about? The cursor is set within gnome
lol It's not a system change. The fonts.. omfg.. Slackwares ugly
ass fonts. Hey you want them.. keep them. Let's see... security..
oh yeah... Ummm "REMOVE PAM" Damn that was easy.. Glad I couldn't
think of that. From what I see here guy.. You probably should
be on XP if you can't figure this basic stuff out.

My system. Not Dlg's.


Simple

Easy

Understand?

Or do you like to argue?

I change settings in my system. Not another program.

But, I guess you don't mind it. That's fine with me. I won't put up with it.
Config files that shouldn't have been messed with to begin with. You made my point.
You're right. I change them. But not another program will change them "for me".

It don't change system settings, one pack, which is easily removed
by the way, gives users permissions.

Simple

Easy

Understand?

And please don't claim that to be your system. Sounds more like
it's Pats system. Lemme guess, you are also one of them morons
that run web/ftp/mail servers from the same box your desktop is
on so you are worried about security. Maybe I'm wrong on that,
but chances are I'm not.

Exactly which rc and conf files are you referring to? ...and more importantly, which distro are you talking about? It can't be Slackware.

Dropline installs/modifies *no* configuration files that it didn't bring in itself as a part of the related package, which it does in the exact same way that Slackware does...

The ONLY exception to this rule is rc.4, which is slightly modified so that GDM is looked for in /usr/sbin/ instead of /usr/bin. Being that it's a sysadmin-type binary, and that it's _normal installation location_ is /usr/sbin, this is a place where Dropline is probably slightly more correct than Slackware (god's forbid!). Even if you were to remove Dropline and then install another GDM, the script will *still* behave properly with that modification in place, since we don't even take out the later invocation of it as /usr/bin/gdm.

Beyond that the only thing else in there that's ever been modified was rc.local, which I *personally* handled fixing recently so that we don't have to mess with it for hal/messagebus to function properly. Dropline now drops a few files into the sysvinit directories, and if you don't like those, *complain to Pat to remove rc.sysvinit*. At the moment there's just one lonely little stanza in rc.local to kill off stale PAM lockfiles which might prevent console ownership from taking place when someone logs in at the console. These lockfiles are only left behind when you accidentally power the machine off while a user is logged in, so they're not much of an issue in any case.

Now... Stop talking through your hat.