Arch-projects

Download

arch-projects@lists.archlinux.org

1 participants
2142 discussions

[arch-projects] Proposal for additional gcc packages
by Jason Chu 25 Aug '04

25 Aug '04

This is something I've been kicking around for a bit. Having other gcc packages like gcc-f77 and gcc-java would be helpful, 1) to shut people like this up (http://bbs.archlinux.org/viewtopic.php?t=6376) and 2) for people who actually need a f77 compiler (or a java compiler or whatever). My idea goes something like this. Don't touch the gcc package. Instead, make a similar PKGBUILD that just compiles the additional languages. Compare that package's file list to the gcc package's file list and cull out the duplicates. As long as the existing gcc package doesn't store a list of compiled languages, then it should work. I've already built a gcc-f77 package based around this idea and gcc-java will soon follow. I do lack the skills to properly test the gcc-f77 package, though it is available here: http://xentac.net/~jchu/gcc-f77-3.4.1-2.pkg.tar.gz The way I've explained it so far, you may be wondering about gcc upgrades. The gcc-f77 package depends on gcc=$pkgver, so if gcc is upgraded before gcc-f77, pacman will complain. In that way, you'll never have conflicting package versions installed at the same time. The only drawback to this approach that I've found is that you compile gcc multiple times. The only solution to that is make a method to build multiple packages from one PKGBUILD. This goes against the KISS design philosophy and would break a lot of stuff for only a few benefits (a few packages). Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are. My old gpg key expired, the new one is available from keyservers. I was stupid enough not to realize this before it was too late, so I am not able to sign my new key with my old key. If this assurance isn't enough, please contact me.

3 6

[arch-projects] Initial Announcement
by Jason Chu 24 Aug '04

24 Aug '04

Hello to all, This will be my first email with my new gpg key... now, on to business. This mailing list was originally created because people finally were interested in helping out with interesting things in Arch. Up until that point, most of the drive for interesting things came directly from me, so I kept a lot of my ideas to myself. Now that other people have shown interest, we (the Arch Linux elite) have started this mailing list to propose, discuss, and plan interesting technology enhancements for Arch Linux. So that people don't have to ask a lot of the same questions about an idea when it is first proposed, I will put forward a format for all proposals to follow. Not so much a layout format, but at least an informational content format. All proposals should contain a description of the idea, an explaination of how it will help improve Arch, thoughts about how you came to that conclusion (goes with the explaination), and proposed technologies. The proposed technologies are optional; some ideas need a lot of research or the proposer lacks the necessary skill set. After something is proposed, discussion will commence. Remember to be courteous and professional. I don't want to be putting out flame wars just because two people don't like each other's mothers. This list will be *the* place to find dedicated, smart, and hard working people interested in solving interesting problems to help better Arch. I don't want this list to become another hey-I've-got-a-really-great-idea-to-make-things-really-really-super-awesome-who-wants-to-do-all-the-work list. People with ideas like that can go to the arch mailing list. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are. My old gpg key expired, the new one is available from keyservers. I was stupid enough not to realize this before it was too late, so I am not able to sign my new key with my old key. If this assurance isn't enough, please contact me.

1 0

Jump to page: