| 1 |
On 14/02/15 05:08, James wrote: |
| 2 |
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
... |
| 6 |
>> Any special reason why you don't instead download the sources and build |
| 7 |
>> them yourself with PREFIX=/usr/local ? |
| 8 |
> |
| 9 |
> Lots of errant codes flying everywhere so you have to pull a code audit |
| 10 |
> to see what's in the raw tarballs before building. That takes way too much |
| 11 |
> time. I'm working on setting up several more workstations for coding to |
| 12 |
> isolate them from my main system. This approach you suggest is: error prone, |
| 13 |
> takes too much time, and I'm lazy and sometimes even stupid. |
| 14 |
> I need a structure methodology to be a one man extreme_hack_prolific |
| 15 |
> system that prevents me from doing stupid things, whilst I'm distracted. |
| 16 |
> |
| 17 |
|
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
rpm is just a wrapper around a an archive with instructions on how to |
| 22 |
build and or install it. I have more experience with rpm's but I |
| 23 |
believe debs are the same. Just unwrap your .rpm/.deb file of choice |
| 24 |
and install it manually (the binaries/code are usually in a zip inside |
| 25 |
the rpm). You should in most cases also be able to get a source rpm |
| 26 |
(which I suspect you are talking about anyway, but binaries do work deps |
| 27 |
permitting. |
| 28 |
|
| 29 |
you can install rpm and then install your package via rpm - seem to |
| 30 |
remember doing this with .debs somehow too. deps are a problem but |
| 31 |
usually workable. |
| 32 |
|
| 33 |
and why set up a workstation? - this sort of thing is tailor made for |
| 34 |
vm's. Create a base for your experiments with essential packages, |
| 35 |
settings etc, snapshot it (golden master) and then throwaway->restore |
| 36 |
when finished with that iteration. |
| 37 |
|
| 38 |
There are package managers besides gentoo/protage that can do a source |
| 39 |
build/install and track the files on gentoo - though portage will not |
| 40 |
know about it (rpm is one :) |
| 41 |
|
| 42 |
and lastly, what do mean error prone? - to me a manual install is the |
| 43 |
ONLY way you can build a proper ebuild that catches most of the |
| 44 |
problems. In the (admittedly few) ebuilds I have done an occasional |
| 45 |
human error is nothing compared to system problems for a difficult package. |
| 46 |
|
| 47 |
BillK |
Archives