Re: [gentoo-dev] why is the security team running around p.masking packages

[james]

On 07/05/2016 08:05 AM, Rich Freeman wrote:
> On Tue, Jul 5, 2016 at 8:58 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote:
>> Big difference. Gentoo's tree is not hosted on github, and infra isn't
>> going to put an attic equivalent there.
>>
>
> Either way admittedly git makes finding deleted files a bit of a pain.
> However, it is certainly possible:
> https://stackoverflow.com/questions/7203515/git-how-to-search-for-a-deleted-file-in-the-project-commit-history
>

OK, but with the attic, you can browse by category, read descriptions to 
get an idea of what is available. Correct me if I'm wrong, but with 
github, you have to know the name of the packages and that is a 
limitation when looking  back. The attic just makes browsing and 
retrieval a snap, imho.

> I think this is just one more reason that "power users" should
> seriously consider just syncing from git.  It is really useful to have
> a git repo, and once you have one, it is going to be a lot faster to
> just use it as your daily driver since it syncs so quickly/etc


OK, I'll give that a whirl. But if I want to go casually looking at old 
codes, removed from the tree, that I have never used before, but  are 
vaguely referred to in some old post, how do I do that with git?
For example, I have conversed on numerous occasions with the old physics 
professor that wrote sys-cluster/wulfware. We have prospectives that are 
similar. Although he does not actively, at this time, support wulfware, 
he has architected  a more conservative approach to HPC than many of the 
current, more-prominent projects.  He has quite a proposal for me to 
move the code forward, should I want to take it over. Yet, a 
tree-cleaner probably has marked it for removal.

Old code is often wonderful, ymmv. It's old school, 'C' centric and 
there are many other old useful codes. Not that this reference is any 
big deal, but there is a lot more than me out there with similar 
beliefs. It's exciting to see something old (PVM) return in part as  a 
new project (OrangeFS). Oh, OrangeFS is all the new-rage with some HPC 
folks and it making a return via kernel-4.6 (I believe).

So, I guess I'll read up and try to set up my own git repo, so I do not 
have to delete files as they are pruned from the official portage tree.
That is what you are suggesting, right?

In a way I have been doing that manually by syncing up a separate 
/usr/portage/distfiles/   and putting lots of codes into 
/usr/local/portage/. I would hope, some devs would put thought into this
and formalize a few methods and a document so that in effect, I can 
manage my own gentoo attic, going forward, and likewise others could 
too, or a partial archive, according to their interests.

Granted my ignorance of git is a big factor here, so do not be shy to 
suggest reading materials.... Often I read docs on git and well, I might
as well be reading Hieroglyphics. It's easier to follow examples, imho, 
and that makes support more straight forward and consistent should 
others need to retrieve old ebuilds and source files.


Thanks for the info and ideas.
James