devel July 2003

devel@lists.fedoraproject.org

70 participants
48 discussions

Re: How to Propose Packages?
by Féliciano Matias 22 Jul '03

22 Jul '03

Le mar 22/07/2003 à 21:58, Havoc Pennington a écrit : > On Tue, Jul 22, 2003 at 12:47:47PM -0700, Howard Owen wrote: > > How do you propose a package for inclusion under the new regime? > > I have an auditing package called sudoscript that's been in contrib > > since 1.0.something. It's now at version 2.2.1 with 3.0 in testing. > > I'd like to maintain in RHL. What's the process? > > Well, that's the catch. We don't have the infrastructure in place yet. > > We've started by putting up a lot of our internal devel docs on > rhl.redhat.com, and moving our devel discussion from internal forums > to rhl-devel-list and #rhl-devel. So joining those is probably a good > step. > > The problem is that our infrastructure for all the aspects of > maintaining a package is still partially internal. So over the next > months, we will be trying to break down the barriers to external > contribution. > > Right now, to accept an external package we'd basically need someone > internal to act as a proxy for you to build your SRPMs, we may do this > for two or three packages, but it isn't going to scale at all. > Can we expect that this infrastructure will be an "open projet" in the RedHat Linux Projet ? > Havoc > > > -- > Rhl-list mailing list > Rhl-list(a)redhat.com > http://www.redhat.com/mailman/listinfo/rhl-list -- Féliciano Matias <feliciano.matias(a)free.fr>

2 1

Adding new packages to RedHat Linux
by Michael A. Koziarski 22 Jul '03

22 Jul '03

Hi, I'm a user of gtkmm for my internal development work, redhat releases currently do not include a version of gtkmm-2 and this causes me a lot of problems. Judging by the following bugzilla entry, I'm not alone. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82473 With the announcement of the redhat linux project I was wondering what would be required to get gtkmm (and the gnomemm packages) added to the redhat linux project's releases. Some of us on the mailing list have already indicated that we'll be able to help with testing the spec files, builds, dependencies etc. http://mail.gnome.org/archives/gtkmm-list/2003-July/msg00185.html There's still some work to be done with the spec files, but the newly published guidelines make this much easier to do. Once we have the spec files updated and tested by a few of us with the new beta, what is the process we should follow to get the package officially included? Cheers Koz ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

Re: other window managers
by Chris Ricker 22 Jul '03

22 Jul '03

On Tue, 22 Jul 2003, Havoc Pennington wrote: > On Tue, Jul 22, 2003 at 10:40:21AM -0700, Lawrence Mao wrote: > > Just wondering whether RedHat or somebody else is > > thinking about adding other lightweights window > > managers besides that BlueCurve like Xfce, Fluxbox, or > > Fvwm! BlueCurve is nice but I don't need all those > > bells and whistles. I want something (window manager) > > that is fast and doesn't take up a lot of system > > resources... > > > > We aren't thinking of doing this ourselves at Red Hat, but alternative > WMs are a prime example of the kind of package we'd like to see added > to Red Hat Linux by others. <hijacked this thread to a more appropriate mailing list ;-) > Okay. I've got a fairly complete package of Openbox <http://www.openbox.org/> -- IMHO probably the best of the Blackbox family (blackbox, fluxbox, etc.) -- that I put together for fedora. How do I go about submitting this package? I'll bugzilla it against the distro for now, but what happens then? later, chris

1 0

xdirectfb
by Vincent 22 Jul '03

22 Jul '03

Is xdirectfb installed in X by default? if not it should be, It's a tiny patch but alot of work to recompile all of X every time there is a RH update for those of us on low-end machines, or just not tech savy enough to install it. http://www.directfb.org/xdirectfb.xml

1 0

External CVS access
by Paul Nasrat 22 Jul '03

22 Jul '03

As documented: http://rhl.redhat.com/projects/additional-projects/kudzu/ [paul@uruk src]$ export CVSROOT=:pserver:anonymous@rhlinux.redhat.com:/usr/local/CVS [paul@uruk src]$ cvs -z3 login Logging in to :pserver:anonymous@rhlinux.redhat.com:2401/usr/local/CVS CVS password: cvs [login aborted]: connect to rhlinux.redhat.com(66.187.233.241):2401 failed: Connection timed out I assume this just isn't setup yet. Paul

4 4

docs in downloadable format?
by Chris Ricker 22 Jul '03

22 Jul '03

I'm browsing through http://rhl.redhat.com/ -- looks good. Under the Participate section, there's a "Developer's Guide" and a "Documentation Guide". Any chance of those being posted in a format that's easy to download / print (pdf, single inline html, or similar)? later, chris

7 8

AN IDEA FOR A BIG PROJECT!
by euler euler 22 Jul '03

22 Jul '03

Hello everyone, I have a good idea for a big project, any developer care to listen? The development of Linux is always depend on chance, not certainity. It maybe the biggest hinderance for Linux to become a real competitive OS. For Linux to run well, either kernel and softwares has to be tested on many different hardwares platform (combination of CPU and other components). Currently, if some developer has developed a program, s/he will post it in E-mail/mailing list, then wait for someone of unknown hardware platform to test it. S/he: 1.) Can NOT TARGET a certain hardware platform for beta-test, it all depend on his/her luck; 2.) Can NOT expect a response within certain time limit; 3.) May NOT able to test the program on ALL hardware platform for a long time. To overcome this, how do we TURN every Linux user automatically a beta-tester without ANY technical background? The answer lie in a specially made kernel: It will allocated a protected area of CPU which is open for ALL developer in the world for beta-testing his/her program. For instance, if a developer is writing a program called K which he want to test on hardware platform A,B and C, he will just have to activate a searcher in his Linux, then the searcher will look at the hardware profile of all Linux in the world to find a match; if a match is made, then the program is travel through www to these specific computer; the program is executed in the special area of CPU which will NOT affect what the owner is doing, then the result is sent back to the original developer for comparison. Now the developer can get results for ANY specified hardware platform in an expect time, it does NOT depend on luck or chance! S/he could get MANY MANY MANY results from MANY MANY MANY different hardware platform within a short time, and s/he should NEVER worry about un-tested platforms since the whole Linux community's CPU is open for him/her. Moreover, instead of waiting for some human to pick it up from a list then test it then post the result, everything is now done AUTOMATICALLY without the help of owner, the developer can COUNT on getting the result within hours or even minutes, how much it will SPEED UP the Linux development? Any taker of this idea? Anyone want to write a new chapter of Linux development? I believe developmental process is key aspect to improve and refine if Linux want to stay ahead. Thanks in advance! Best Regards, Euler Cheung Project Manager LinuxLiveCD.com

2 1

Announcing a beta release of Red Hat Linux: Severn
by Bill Nottingham 21 Jul '03

21 Jul '03

Thank you gentlemen. This is rumor control. Here are the facts. As some of you know, new Red Hat Linux Beta bits crash landed here at 1000 on the morning watch. There was one survivor. Two dead processes, and a daemon that was hopelessly smashed beyond repair. The survivor is called SEVERN. It's that time again. (Time to floss?) (Time to make a gooky?) No, it's time for a Red Hat Linux Beta, named SEVERN. "I just want to say that I took a vow of stability. That also includes betas. We all took the vow. Now let me say, that I for one, do not appreciate Company policy allowing beta bits to freely intermingle..." "Cheeky bastard, right sir?" "What brother means to say is ... We view the presence of any outside OS, beta, as a violation of the stability, a potential break in the spiritual unity." We are well aware of your feelings in this matter. You will be pleased to know that I have requested a testing team - Hopefully, they will be here inside of a few hours and evaluate it A.S.A.P. As always, betas such as SEVERN are not intended for use on production environments. Use as such could lead to your machines being slaughtered like pigs by the dragon. Or just public laughter. Problems with SEVERN should be reported via bugzilla, at: http://bugzilla.redhat.com/bugzilla/ What's its development status? "It doesn't seem too horrendously in flux. Difficult at this moment to make a specific diagnosis." Among other things, SEVERN has: - a new graphical boot - GCC 3.3 - an updated 2.4.21 kernel - updated Evolution and Mozilla - and more! Will it live? "Yes, I should think so." Look, none of us here is naive. It's in everybody's best interests if this beta doesn't come out into production until the testing team is through with it. And certainly not without the proper qualification and bug reports. Right? So we should all stick to our set routines and not get unduly agitated. Correct? All right. Thank you gentlemen. Speaking of unduly agitated... there's lots of rumors going on about Red Hat Linux. We've been doing it for nearly ten years now, and in that time, there's been various changes. From rpp to RPM, from Red Hat Commercial Linux to Official Red Hat Linux, from 'install' to anaconda. And now, we're making another change. We changed the rules. We said our Linux should be your Linux. Just as most of the software in Red Hat Linux is developed in an open fashion, so should Red Hat Linux itself; driven by those who develop, test, document, and translate. To accomplish this, we're opening up our process. Now this is an evolution, not a revolution. The first steps will be moving much of our development discussions and schedules external, via mailing lists and other means, and including external developers in the process of making technical decisions. More will be done from there. Red Hat Linux will remain as it has been; a freely available general purpose operating system, released on the average every six months. For more information, see: http://rhl.redhat.com/ For discussion of SEVERN, send mail to: rhl-beta-list-request(a)redhat.com with subscribe in the subject line. You can leave the body empty. Or see: https://listman.redhat.com/mailman/listinfo/rhl-beta-list/ As always, you can get SEVERN at redhat.com, specifically: ftp://ftp.redhat.com/pub/redhat/beta/severn/ Or the following mirrors: North America: United States: ftp://moni.msci.memphis.edu/pub/redhat/linux/beta/severn/ http://moni.msci.memphis.edu/pub/redhat/linux/beta/severn/ ftp://linux.stanford.edu/pub/mirrors/redhat/linux/beta/severn/ ftp://ftp.cse.buffalo.edu/pub/RedHat/redhat/linux/beta/severn/ ftp://mirror.eas.muohio.edu/mirrors/redhat/linux/beta/severn/ ftp://mirrors.secsup.org/pub/linux/redhat/beta/severn/ ftp://redhat.dulug.duke.edu/pub/redhat/linux/beta/severn/ ftp://mirror.hiwaay.net/redhat/redhat/linux/beta/severn/ http://mirror.hiwaay.net/redhat/redhat/linux/beta/severn/ http://www.gtlib.cc.gatech.edu/pub/redhat/linux/beta/severn/ ftp://ftp.gtlib.cc.gatech.edu/pub/redhat/linux/beta/severn/ rsync://rsync.gtlib.cc.gatech.edu/redhat/linux/beta/severn/ Canada: ftp://less.cogeco.net/pub/redhat/linux/beta/severn/ ftp://ftp.nrc.ca/pub/systems/linux/redhat/ftp.redhat.com/linux/beta/severn/ South America: Brazil: http://bastion.las.ic.unicamp.br/pub/redhat/linux/beta/severn ftp://bastion.las.ic.unicamp.br/pub/redhat/linux/beta/severn Chile: ftp://ftp.tecnoera.com/Linux/redhat-beta/severn/ Europe: Austria: ftp://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ http://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ rsync://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ Czech Republic: ftp://sunsite.mff.cuni.cz/MIRRORS/ftp.redhat.com/redhat/linux/beta/severn/ ftp://ultra.linux.cz/MIRRORS/ftp.redhat.com/redhat/linux/beta/severn/ ftp://sunsite.cnlab-switch.ch/mirror/redhat/linux/beta/severn/ ftp://ftp.linux.cz/pub/linux/redhat/linux/beta/severn/ ftp://ftp6.linux.cz/pub/linux/redhat/linux/beta/severn/ Denmark: ftp://klid.dk/pub/redhat/linux/beta/severn/ Germany: ftp://ftp.tu-chemnitz.de/pub/linux/redhat-ftp/redhat/linux/beta/severn/ http://wftp.tu-chemnitz.de/pub/linux/redhat-ftp/redhat/linux/beta/severn/ ftp://ftp.informatik.uni-frankfurt.de/pub/linux/Mirror/ftp.redhat.com/linux… ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/redhat/linux/beta/severn/ Ireland: ftp://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ http://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ rsync://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ Netherlands: ftp://ftp.nluug.nl/pub/os/Linux/distr/RedHat/ftp/redhat/linux/beta/severn/ ftp://ftp.surfnet.nl/pub/os/Linux/distr/RedHat/ftp/redhat/linux/beta/severn/ ftp://alviss.et.tudelft.nl/pub/redhat/beta/severn/ Poland: ftp://sunsite.icm.edu.pl/pub/Linux/redhat/linux/beta/severn/ rsync://sunsite.icm.edu.pl/ftp/pub/Linux/redhat/linux/beta/severn/ http://sunsite.icm.edu.pl/pub/Linux/redhat/linux/beta/severn/ Romania: ftp://ftp.iasi.roedu.net/pub/mirrors/ftp.redhat.com/pub/redhat/linux/beta/s… http://ftp.iasi.roedu.net/mirrors/ftp.redhat.com/pub/redhat/linux/beta/seve… rsync://ftp.iasi.roedu.net/ftp.redhat.com/pub/redhat/linux/beta/severn/ Turkey: ftp://ftp.linux.org.tr/pub/redhat/beta/severn/ United Kingdom: http://zeniiia.linux.org.uk/pub/distributions/redhat/beta/severn/ ftp://zeniiia.linux.org.uk/pub/distributions/redhat/beta/severn/ rsync://zeniiia.linux.org.uk/ftp/pub/distributions/redhat/beta/severn/ Asia/Pacific: Australia: http://planetmirror.com/pub/redhat/linux/beta/severn/ ftp://ftp.planetmirror.com/pub/redhat/linux/beta/severn/ http://mirror.aarnet.edu.au/pub/redhat/linux/severn/ ftp://mirror.aarnet.edu.au/pub/redhat/linux/severn/ Japan: ftp://ftp.sfc.wide.ad.jp/pub/Linux/RedHat/linux/beta/severn/ Singapore: ftp://ftp.oss.eznetsols.org/linux/redhat/linux/beta/severn/ rsync://rsync.oss.eznetsols.org/linux/redhat/linux/beta/severn/ One additional feature provided by the Linux community is the availability of SEVERN via BitTorrent. http://torrent.dulug.duke.edu/severn-binary-iso.torrent http://torrent.dulug.duke.edu/severn-source-iso.torrent RPMS for Red Hat Linux 7.3 through 9 of BitTorrent are available from: http://torrent.dulug.duke.edu/btrpms/ Usage is simple: btdownloadcurses.py --url http://URL.torrent Allow incoming TCP 6881 - 6889 to join the torrent swarm. http://torrent.dulug.duke.edu/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel July 2003