Motion picture studios and software and video game publishers have protected their works for years, and no one has even (thought) to claim that doing so was inappropriate, let alone unlawful.
I suppose that's why every single real copy protection for software has been abandoned, right? Anyway, the Jargon File defines copy protection as:
copy protection n.
A class of methods for preventing incompetent pirates from stealing software and legitimate customers from using it. Considered silly.
Update:Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
I have a script I think will work; email me (jcast at ou dot edu) if you want a copy./. thinks it has too many ``junk characters''.
Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
-devel can be handled by examining the extension and/or install directory of the file, right? And as for the other point (about modules), if you have control of the source code's organisation, you can put each module into a separate sub-directory and split based on source sub-directory, no? There may be times you can't come up with a general rule for splitting files into packages, but I don't think that's the general case.
Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
And while I hate to admit it, shared libraries do suck long term when building applications. The dependencies become nightmarish because you code against specific versions and assume certain things.
Translation: I don't know how to write portable code.
I would rather simply static link it and be done with it.
Translation: I'm lazy.
Granted, documentation of what's portable and supported could be drastically improved. But if you really can't keep your system working with newer versions of libraries, there's pilot error somewhere. Pilot error is not a problem with.so files; it's a problem with pilots. To eliminate it, find perfect pilots:)
Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
However, if you want to split things into more than one binary pacakge,
Why?
Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
I think this is a cleaner version of what you want: Create two files,/etc/prefixen and/etc/paths./etc/prefixen (for example) might look like this: / /usr /usr/mozilla
/etc/paths looks like this: PATH/bin LD_LIBRARY_PATH/lib
Then, on startup,/etc/profile reads these files in, and sets things up appropriately (i.e., PATH becomes/bin:/usr/bin:/usr/mozilla/bin and LD_LIBRARY_PATH becomes/lib:/usr/lib:/usr/mozilla/lib). Then, put mozilla under/usr/mozilla/bin and put its libraries under/usr/mozilla/lib. When mozilla is installed, just make sure/usr/mozilla is in/etc/prefixen. Under/usr/mozilla/libexec (or maybe/tmp/exec, or wherever), put a shell script that reads/etc/paths and manually inserts/usr/mozilla into them. Then, tell the user to source that file before running mozilla. And of course, at the next login sh will automatically add/usr/mozilla to all the right paths.
Re:standardized Linux configuration files...
on
Is RPM Doomed?
·
· Score: 2, Insightful
I think the suggestion was to make a standardised GUI. Those who want to use vi, emacs, whatever still could, and the basic system would still work. Newbies, on the other hand, can use a cleaned-up interface, which I predict would spread across all Un*x variants if done right. After all, isn't the point of slowly-evolving that you're never done, never perfect?
Re:standardized locations, etc.
on
Is RPM Doomed?
·
· Score: 1
Duplicate libraries eat RAM. RAM eats your budget. Having your budget eaten sucks. Clear?
The key difference is that with corporations (minus government involvement), any one can join with enough hard work. You can make an impact one person at a time. Whereas with the government, you basically have to make your impact one majority at a time---otherwise nothing will happen.
Please don't tell me you think everything should go over HTTP (which not even M$'s people believe---look it up, it was on/. a while back) just because some idiots don't know how to configure a firewall properly.
Well, the whole point of s.f. is that plausible but un-invented stuff is allowed. Unplausible stuff is not.
Re:Differences appear minor
on
Gnome 2.0 RC1
·
· Score: 1
Absolutely---most of the GNOME libraries are completely useable outside of GNOME, and (often) outside of each other. Consolidating them would be the worst thing that could happen for cmd line developers!
``Computer Science is no more about computers than astronomy is about telescopes''---Dijsktra (more or less). If you want to learn programming without understanding C.S., go take MIS.
p.s.:/.: Its Friday, I'm tired; I'm going as slow as I can. And STOP CALLING ME COWBOY!
Slashdot Mirror
By the way, I'd like to congratulate all y'all leftists---six replies and two form a valid argument!
Got a bit of evidence the media is not liberal (as in left of the average American, not left of the average /.er) or not raised on Watergate?
A C.S. Research Assistant braindead hick.
Vince. Foster. Is. Dead.
I never said the media ignored Democrat scandals. I said they give far more attention to Republican scandals.
The media is composed of Democrats raised on Watergate. That's why they only care about scandals in Republican administrations.
Sorry if it hurts all y'all leftists, but its true.
I suppose that's why every single real copy protection for software has been abandoned, right? Anyway, the Jargon File defines copy protection as:
I think Sherman's claim is pretty specious.
Only if you base it around GNU, nitwit.
I have a script I think will work; email me (jcast at ou dot edu) if you want a copy. /. thinks it has too many ``junk characters''.
-devel can be handled by examining the extension and/or install directory of the file, right? And as for the other point (about modules), if you have control of the source code's organisation, you can put each module into a separate sub-directory and split based on source sub-directory, no? There may be times you can't come up with a general rule for splitting files into packages, but I don't think that's the general case.
Translation: I don't know how to write portable code.
Translation: I'm lazy.
Granted, documentation of what's portable and supported could be drastically improved. But if you really can't keep your system working with newer versions of libraries, there's pilot error somewhere. Pilot error is not a problem with
Why?
I think this is a cleaner version of what you want: Create two files, /etc/prefixen and /etc/paths. /etc/prefixen (for example) might look like this:
/bin /lib
/etc/profile reads these files in, and sets things up appropriately (i.e., PATH becomes /bin:/usr/bin:/usr/mozilla/bin and LD_LIBRARY_PATH becomes /lib:/usr/lib:/usr/mozilla/lib). Then, put mozilla under /usr/mozilla/bin and put its libraries under /usr/mozilla/lib. When mozilla is installed, just make sure /usr/mozilla is in /etc/prefixen. Under /usr/mozilla/libexec (or maybe /tmp/exec, or wherever), put a shell script that reads /etc/paths and manually inserts /usr/mozilla into them. Then, tell the user to source that file before running mozilla. And of course, at the next login sh will automatically add /usr/mozilla to all the right paths.
/
/usr
/usr/mozilla
/etc/paths looks like this:
PATH
LD_LIBRARY_PATH
Then, on startup,
I think the suggestion was to make a standardised GUI. Those who want to use vi, emacs, whatever still could, and the basic system would still work. Newbies, on the other hand, can use a cleaned-up interface, which I predict would spread across all Un*x variants if done right. After all, isn't the point of slowly-evolving that you're never done, never perfect?
Duplicate libraries eat RAM. RAM eats your budget. Having your budget eaten sucks. Clear?
The key difference is that with corporations (minus government involvement), any one can join with enough hard work. You can make an impact one person at a time. Whereas with the government, you basically have to make your impact one majority at a time---otherwise nothing will happen.
Well, his parent said ``money-grubbing whore site''. Not the most neutral of word choices, no?
Why does being rewarded for providing a useful service to a lot of people constitute being a ``sellout''?
Please don't tell me you think everything should go over HTTP (which not even M$'s people believe---look it up, it was on /. a while back) just because some idiots don't know how to configure a firewall properly.
``Would take a ton of effort''---who wants to bet it would be easier just to start over and wrap Gecko in MFC, going for maximum Windows integration?
No, people who don't like nerds give us a bad name. We give ourselves good names, the rest of the world just hasn't noticed yet.
Well, the whole point of s.f. is that plausible but un-invented stuff is allowed. Unplausible stuff is not.
Absolutely---most of the GNOME libraries are completely useable outside of GNOME, and (often) outside of each other. Consolidating them would be the worst thing that could happen for cmd line developers!
``Computer Science is no more about computers than astronomy is about telescopes''---Dijsktra (more or less). If you want to learn programming without understanding C.S., go take MIS.
/.: Its Friday, I'm tired; I'm going as slow as I can. And STOP CALLING ME COWBOY!
p.s.:
I don't (generally) type faster than write---because I think faster (yes, that much faster) when I've got something between my fingers :)