public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: rpm or deb package installs
Date: Fri, 13 Feb 2015 21:08:55 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150213T205104-82@post.gmane.org> (raw)
In-Reply-To: 54DE417B.1030706@gmail.com

Alan McKinnon <alan.mckinnon <at> gmail.com> writes:


> I doubt dpkg and rpm aren't going to be much use to you, unless you
> really want to run two package managers. Besides, both are not
> especially useful with the front ends apt* and yum.

I'd just use those to unpackage and maybe preprocess some of the codes.

Agreed. I do not want a full blown deb or rpm package manager just
a way to install and evaluate some of those codes before beginning a more
arduous  and comprehensive task. Maybe I should just put up a RH/centos box
and evaluate codes there. It seems *everything* I want to test and look at
in the cluster and hpc world, as a rpm or deb package; so I'm looking for a
time saver, to surf thru the myriad of codes I'm getting; many look very
cool  from the outside, but once I run them, they are pigs.......

Then a slick way to keep them secure and clean it out. Maybe I need chroot
jails too? I spend way to much time managing codes rather than I do actually
writing code. I feel confused often and cannot seem to master this
git_thingy.... I have not code seriously in a long time and now it is
becoming an obsession, but the old ways are draining my constitutional
powers.....


> Any special reason why you don't instead download the sources and build
> them yourself with PREFIX=/usr/local ?

Lots of errant codes flying everywhere so you have to pull a code audit
to see what's in the raw tarballs before building. That takes way too much
time. I'm working on setting up several more workstations for coding to
isolate them from my main system. This approach you suggest is: error prone,
takes too much time, and I'm lazy and sometimes even stupid.
I need a structure methodology to be a one man extreme_hack_prolific
system that prevents me from doing stupid things, whilst I'm distracted.


Maybe I should just put up a VM resources on the net, blast tons
of tests thru the vendors hardware and let them worry about the
security ramifications?  Some of it is these codes are based on 'functional
languages' and I just do not trust what I do not fully understand. Stuff
(files etc) goes everywhere and that makes me cautiously nervous. I have
/usr/local for manual work and /usr/local/portage for ovelays (layman) but
it's becoming a mess. There where to I put the work effort that is a  result
from repoman. Those codes seem to be parallel projects often
when the code I'm evaluating needs to be cleaned up or extend to properly
test. Furthermore I have a growing collection of file that result
from kernel profiling via  trace-cmd, valgrind, systemtap etc etc.
As soon as I delete something, I need to re-generated it for one
reason or another...... I just hope that this repo.conf effort
helps be get more structurally organized?  


Did you see/test 'travis-ci' yet? [1] I'm not sure it's the same
on github [2] but some of the devs are using it on github. 



James

[1] http://docs.travis-ci.com/

[2] https://github.com/travis-ci/travis-ci








  reply	other threads:[~2015-02-13 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 14:12 [gentoo-user] rpm or deb package installs James
2015-02-13 18:24 ` Alan McKinnon
2015-02-13 21:08   ` James [this message]
2015-02-13 23:00     ` [gentoo-user] " Neil Bothwick
2015-02-14 14:14       ` James
2015-02-13 23:31     ` Bill Kenworthy
2015-02-14 16:04       ` James
2015-02-14  6:30     ` Alan McKinnon
2015-02-14 14:47       ` James
2015-02-22 13:07       ` Tom H
2015-02-23  5:06         ` R0b0t1

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20150213T205104-82@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox