Construct 3 Pacman

[Anita Damelio]

I am currently using ubuntu but because i wanted to build my own system using XFCE or Gnome i am looking once again at ARCH.

But i find the Pacman package mananger to lack a few options that apt does have... if they are there i cannot find them.

On Debian/Ubuntu the command used is "apt-get build-dep " and the package manager will then tell me all the deps that i need and installs them aswell if i wish.

Is there a way todo the same with the Pacman package manager ? so install only the dependencies of a particular package and not the package itself so i can build it from source ?

Since you say you've looked into Arch in the past, and are strongly considering it now, you oughtta follow the advice of the amply experienced responders here and read the wiki pages on Pacman and Makepkg. These posters have more-or-less answered your questions completely. Since you have shown a genuine interest so far, here's a little more info: The wrappers Mr. Green refers to are an option you can use to deal with the Arch User Repository--you might think of it as a giant PPA, only in the AUR's case all packages are built from source using scripts. For the sake of security and simplicity (refer to the Arch Way in the wiki) Pacman only deals with packages from the binary repos. Makepkg is a tool that uses scripts to build binary packages from source tarballs, which can then be handled by Pacman. Pacman wrappers often simply tie together the two processes. Not only do both tools cover what you're looking to do, but I daresay many, many people do just that regularly. I have half-a-dozen or so packages I build from vcs every week. There you have it. If you do come to Arch, you'll be totally welcome--these folks are great--but you will be expected to do the majority of this sort of research on your own. Hope this helps.

This thread is confusing to someone who doesn't know what the build-dep option to apt-get is. It installs the build dependencies of a package so that it may be built. The usual tool for building packages for Arch Linux is makepkg and it can do this automatically by calling pacman on the user's behalf. The OP is advised to peruse the man pages and wiki a little more, especially the articles on AUR.

You have a similar question to the OP - did you read the answers in this thread? If you are having trouble using makepkg, start your own thread giving the relevant information: the package you're trying to build, the dependencies that are missing, and any error messages you recieve.

Hi rhoit, you need to make a PKGBUILD. There may already be one for the package you are trying to install. Search the repositories and search AUR. If none exist, you can request someone else build one for you (AUR Issues, Discussion & PKGBUILD Requests) or make a PKGBUILD yourself. As I wrote almost two years ago, read the man pages. If something is unclear, start a new thread and ask about that.

Closing,

alsa-lib is required for gcc-gcj. Pacman wants to install alsa-lib-1.0.14-5. But, I have already installed alsa-lib-1.0.15rc1 outside of pacman. So, pacman doesn't think it's installed. Is there a way to make pacman think it's installed? Also, it would be good if it's ignored in future system updates too.

If you really want to make pacman think that alsa-lib is installed you'd need to make a PKGBUILD for a package called alsa-lib and install it - for example package what you installed outside of pacman as alsa-lib. That would be the proper way to do it, in fact. I can't say for sure, but I imagine that it would be very easy to adjust the standard Arch alsa-lib PKGBUILD to use 1.0.15rc1 as the source, probably as easy as updating the version number and md5sum in the PKGBUILD.

Download, untar, change into the created directory and run "makepkg" and then install the package with pacman -U alsa-lib-1.0.15rc1.tar.bz2. That should create and install an alsa-lib package for you.

The package is based on default Arch alsa-lib PKGBUILD but uses the version of sources you need (1.0.15rc1). FYI - I had to remove one patch which wouldn't apply cleanly to this version of the source, but then if you had installed it with make/make install you wouldn't have that patch anyways. The package does include "python2.5.patch" just like the Arch package.

Ideally you would uninstall the package you have installed from source first (by running "sudo make uninstall" - most likely - from the directory where you installed it from originally). This is not completely necessary though - I think you should be able to install it anyways, and in case it complains that files already exist you can always use pacman -Uf to force overwriting files.

Thanks, I got it. Was hoping for something a bit simpler, so will have to put this aside until I can spend more time on it. I'm sure it's not complicate, once you understand it. So, anyway, go ahead and remove it.

Like I said - the easy workaround, for now at least, would be to try and install whatever package you're installing, see what dependencies it requires and wants to install, cancel and install the dependencies by hand (minus alsa-lib) and finally install the package with ignore dependencies option.

As far as ABS/PKGBUILDs are concerned - they are one of the best, if not the best feature of Arch. Indeed, they are not complicated, but you need to read the wiki and experiment a bit first before you'll get how they work... It's definitely worth learning though, IMO, they are a very powerful tool (you can use them to customize packages, like this one, or a kernel for example, build your own packages and so forth). Anyways, good luck.

I am trying to move from one arch install a (partitioned one) to another (a less-partitioned one) on my computer and I want a similar set up. So I was wondering if there was a simple way to get pacman to install the same packages.

Here we only get the packages from the list are available from pacman. That is done with the comm -12 file1 file2 command. The -12 flag suppresses unique lines in file 1 and 2 and leaves us with the intersection of the two files; i.e., the installable packages.

That way they'll also get tracked like any other package. If the reason for this mode of operation was a broken system, just run pacman afterwards (when you can) and the reinstallation will take care of tracking.

On line 76, your checkPixelsPacman() function is calling the keypressed() function to MOVE Pacman in addition to setting his direction. What you should really do is only set the direction in keyPressed() (since that's all pressing a key should actually do, right?), and then try to update pacman's position is some other function.

I am proud to make publicly available an Atari 7800 PacmanConstruction Set. For those who previously tried my Beef Drop Construction Set, I tried to get to make it as simple as possible to hack Pacman. With this tool you'll beable to many changes to most aspects of the Pacman series of games such as:Pacman, Ms. Pacman, and Jr. Pacman to create custom hacks of Pacman. Since you can change most aspects of the game, aside from the actual game play, you can create entirely new versions for this classic game.

There is very little you need to do after downloading and running. Basically make sure that pacman constructionset.exe and A78SIGN.exe, included in the download below) are in the same directory. After that everything is optional, but will make your life easier. The first thing you'll want to do is set an emulator to use using the Debug menu and selecting "Set Emulator". I tested this with ProSystem during development, but you can choose whatever you want. You can find some emulators here. The other thing you might want to do is load an external editor such as a hex editor or bit editor like Hack-o-matic 3 so you can make additional modifications, not available from the editor itself. Once set you can test in an emulator by hitting F8 or opening in an editor using F9. Menu items and buttons are also available.

Special thanks to Bob DeCrescenzo for creating the 7800 Pacman series and providing me with all the technical information necessary to create this and Gambler172 for tirelessly testing the last couple months!

Here's another hack for all the Smurf fans, "Papa Smurf in Pacland". This one has all new levels, title screen, graphics, and even the intermission graphics are different. The only thing I really don't like is the 3rd pacman color for the hat is shared with the hidden side border so you see the "red" zones on the left and right hand side.

I'm pretty new to collecting for the Atari 7800 (I'm a 2600 collector) but now seeing this construction set and what can be done with it makes me want to dig deeper into what can be done with the 7800. Thanks for sharing.

3a8082e126