Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 946233 - app-shells/shish-0.7_pre3-r1 directory for local repository
Summary: app-shells/shish-0.7_pre3-r1 directory for local repository
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-10 22:24 UTC by CaptainBlood
Modified: 2024-12-11 00:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
shish ebuild directory for local repository (shish.tar.gz,3.38 KB, application/gzip)
2024-12-10 22:24 UTC, CaptainBlood
Details
shish ebuild directory for local repository (shish.tar.gz,3.40 KB, application/gzip)
2024-12-10 22:48 UTC, CaptainBlood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description CaptainBlood 2024-12-10 22:24:51 UTC
Created attachment 913777 [details]
shish ebuild directory for local repository

All <what_ever> must be replaced by the appropriate value.

1) Download shish.tar.gz

2) Perform commands as root:

mkdir /var/db/repos/<local>/app-shells
tar -xf </path_to_downloaded_shish.tar.gz>archive.tar.gz -C /var/db/repos/<local>/app-shells

3) Allow build as in:
grep -h shish /etc/portage/package.accept_keywords/*
=app-shells/shish-0.7_pre3-r1 **

4) emerge app-shells/shish::<local>
Comment 1 CaptainBlood 2024-12-10 22:48:17 UTC
Created attachment 913778 [details]
shish ebuild directory for local repository

IUSE=diet removed as it seems mandatory.
All IUSE=diet dependent script lines have been kept commented.

IUSE=debug untested.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-12-11 00:48:20 UTC
The ebuild isn't "for a local repository" (that's really up to the person reading it) -- you're submitting a new ebuild presumably as a version bump? What changes did you make?

Or is it intended purely to fix existing issues and it makes no other changes? In that case, it makes sense to post it to an existing bug.

If it purely solves an unreported issue, then please report that issue with logs, and instead include your ebuild which fixes it (describing what you changed) in its comments.