On Friday, 30 Jul 2004, Jim McQuillan wrote:
As you know, the perl script always downloads the latest versions and
installs them. This is exaclty what the "emerge" command in gentoo
does! This causes problems with emerge and the ebuild as the ebuild
will have to be manually updated in order to reflect the newer
versions of individual packages that might not be announced on the
webpage. What is the policy for minor updates to individual
components? Will that be released as a new version?
Can't the email download an updated list of packages, and then
download those packages ?
Well, yes, it could, I suppose. I examined the perl script and I'm
certain that it's easily repeatable inside bash. But the problem is that
it would wreak havoc with the versioning system. Users with the same
emerge would have different programs, and there'd be no way for portage
to know that there is a new version available because portage looks at
the version of a program in order to know if there's a newer version
available or not. Would there be any way to have a minor-minor version?
4.1.0, for example?
I understand if it isn't. Gentoo hardly releases a new version of
Gentoo every time that someone updates a package. As you say in your
web page, LTSP is practically it's own linux distribution. I wouldn't
expect "emerge redhat" or "emerge debian" to work, so it's already a
miracle and a testament to your work that "emerge ltsp" does.
Also, will the 4.1 files be eventually hosted on the sourceforge
server? My ebuild downloads them directly from www.ltsp.org/ltsp-4.1.
While there's no link on the main site to these files, will there be
one once this comes out of beta?
Actually, www.ltsp.org/ltsp-4.1 IS hosted by SourceForge. It's just not
going through their fle release system. Dunno if that helps.
It does. It means that the files aren't going to move any time soon. I
can leave the ebuild as it is.
There's a second solution, though. I could just have the ebuild
download *all* the source files and compile them on the local
machine. While this is how Gentoo is supposed to work, in the case of
LTSP I'm not sure that's a good idea. It might be a complete waste of
resources. It seems to me that there isn't any advantage in compiling
the packages on the server when the packages themselves will be run
on clients. Or am I mistaken in my understanding of LTSP?
Ltsp really needs to be built through the LBE. Trying to force this
into an eBuild type of setup is probably asking for trouble. I'm not
really sure how to handle this. I'm getting hit by Debian folks,
Redhat folks and Suse folks, all trying to figure out how to ship LTSP
packages as part of their distributions. And, to do that, they want
to build with their tools, not mine.
Well, don't worry about that from me! I know just enough C to type
"make" and "make install". No, I followed everyone's advice and bill_c's
ebuilds before me. Download and decompress.
In case anyone's interested, the completed ebuild can be examined at
http://forums.gentoo.org/viewtopic.php?t=204301. Thanks!
Cheers,
Kenn Sebesta
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
