Gentoo Archives: gentoo-commits

From: Aisha Tammy <gentoo@×××××.cc>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/sci:master commit in: /
Date: Thu, 31 Dec 2020 15:44:36
Message-Id: 1609427996.61241c99dd1a94d48783775d505ebaa31a611dce.epsilon-0@gentoo
1 commit: 61241c99dd1a94d48783775d505ebaa31a611dce
2 Author: Aisha Tammy <gentoo <AT> aisha <DOT> cc>
3 AuthorDate: Thu Dec 31 15:19:56 2020 +0000
4 Commit: Aisha Tammy <gentoo <AT> aisha <DOT> cc>
5 CommitDate: Thu Dec 31 15:19:56 2020 +0000
6 URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=61241c99
7
8 remove skeleton ebuild/metadata files
9
10 they are old and duplicate work from ::gentoo
11
12 Signed-off-by: Aisha Tammy <gentoo <AT> aisha.cc>
13
14 skel.ebuild | 162 ------------------------------------------------------
15 skel.metadata.xml | 31 -----------
16 2 files changed, 193 deletions(-)
17
18 diff --git a/skel.ebuild b/skel.ebuild
19 deleted file mode 100644
20 index 0114d8c26..000000000
21 --- a/skel.ebuild
22 +++ /dev/null
23 @@ -1,162 +0,0 @@
24 -# Copyright 1999-2018 Gentoo Authors
25 -# Distributed under the terms of the GNU General Public License v2
26 -
27 -# NOTE: The comments in this file are for instruction and documentation.
28 -# They're not meant to appear with your final, production ebuild. Please
29 -# remember to remove them before submitting or committing your ebuild. That
30 -# doesn't mean you can't add your own comments though.
31 -
32 -# The EAPI variable tells the ebuild format in use.
33 -# It is suggested that you use the latest EAPI approved by the Council.
34 -# The PMS contains specifications for all EAPIs. Eclasses will test for this
35 -# variable if they need to use features that are not universal in all EAPIs.
36 -EAPI=6
37 -
38 -# inherit lists eclasses to inherit functions from. For example, an ebuild
39 -# that needs the eautoreconf function from autotools.eclass won't work
40 -# without the following line:
41 -#inherit autotools
42 -#
43 -# eclasses tend to list descriptions of how to use their functions properly.
44 -# take a look at /usr/portage/eclass/ for more examples.
45 -
46 -# Short one-line description of this package.
47 -DESCRIPTION="This is a sample skeleton ebuild file"
48 -
49 -# Homepage, not used by Portage directly but handy for developer reference
50 -HOMEPAGE="https://foo.example.org/"
51 -
52 -# Point to any required sources; these will be automatically downloaded by
53 -# Portage.
54 -SRC_URI="ftp://foo.example.org/${P}.tar.gz"
55 -
56 -
57 -# License of the package. This must match the name of file(s) in
58 -# /usr/portage/licenses/. For complex license combination see the developer
59 -# docs on gentoo.org for details.
60 -LICENSE=""
61 -
62 -# The SLOT variable is used to tell Portage if it's OK to keep multiple
63 -# versions of the same package installed at the same time. For example,
64 -# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
65 -# with 1.2.2), it would be optimal to instruct Portage to not remove
66 -# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
67 -# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
68 -# emerge clean understands SLOTs, and will keep the most recent version
69 -# of each SLOT and remove everything else.
70 -# Note that normal applications should use SLOT="0" if possible, since
71 -# there should only be exactly one version installed at a time.
72 -# Do not use SLOT="", because the SLOT variable must not be empty.
73 -SLOT="0"
74 -
75 -# Using KEYWORDS, we can record masking information *inside* an ebuild
76 -# instead of relying on an external package.mask file. Right now, you should
77 -# set the KEYWORDS variable for every ebuild so that it contains the names of
78 -# all the architectures with which the ebuild works. All of the official
79 -# architectures can be found in the arch.list file which is in
80 -# /usr/portage/profiles/. Usually you should just set this to "~amd64".
81 -# The ~ in front of the architecture indicates that the package is new and
82 -# should be considered unstable until testing proves its stability. So, if
83 -# you've confirmed that your ebuild works on amd64 and ppc, you'd specify:
84 -# KEYWORDS="~amd64 ~ppc"
85 -# Once packages go stable, the ~ prefix is removed.
86 -# For binary packages, use -* and then list the archs the bin package
87 -# exists for. If the package was for an x86 binary package, then
88 -# KEYWORDS would be set like this: KEYWORDS="-* x86"
89 -# Do not use KEYWORDS="*"; this is not valid in an ebuild context.
90 -KEYWORDS="~amd64"
91 -
92 -# Comprehensive list of any and all USE flags leveraged in the ebuild,
93 -# with some exceptions, e.g., ARCH specific flags like "amd64" or "ppc".
94 -# Not needed if the ebuild doesn't use any USE flags.
95 -IUSE="gnome X"
96 -
97 -# A space delimited list of portage features to restrict. man 5 ebuild
98 -# for details. Usually not needed.
99 -#RESTRICT="strip"
100 -
101 -
102 -# Build-time dependencies, such as
103 -# ssl? ( >=dev-libs/openssl-0.9.6b )
104 -# >=dev-lang/perl-5.6.1-r1
105 -# It is advisable to use the >= syntax show above, to reflect what you
106 -# had installed on your system when you tested the package. Then
107 -# other users hopefully won't be caught without the right version of
108 -# a dependency.
109 -#DEPEND=""
110 -
111 -# Run-time dependencies. Must be defined to whatever this depends on to run.
112 -# The below is valid if the same run-time depends are required to compile.
113 -RDEPEND="${DEPEND}"
114 -
115 -# Source directory; the dir where the sources can be found (automatically
116 -# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
117 -# If you don't need to change it, leave the S= line out of the ebuild
118 -# to keep it tidy.
119 -#S=${WORKDIR}/${P}
120 -
121 -
122 -# The following src_configure function is implemented as default by portage, so
123 -# you only need to call it if you need a different behaviour.
124 -#src_configure() {
125 - # Most open-source packages use GNU autoconf for configuration.
126 - # The default, quickest (and preferred) way of running configure is:
127 - #econf
128 - #
129 - # You could use something similar to the following lines to
130 - # configure your package before compilation. The "|| die" portion
131 - # at the end will stop the build process if the command fails.
132 - # You should use this at the end of critical commands in the build
133 - # process. (Hint: Most commands are critical, that is, the build
134 - # process should abort if they aren't successful.)
135 - #./configure \
136 - # --host=${CHOST} \
137 - # --prefix=/usr \
138 - # --infodir=/usr/share/info \
139 - # --mandir=/usr/share/man || die
140 - # Note the use of --infodir and --mandir, above. This is to make
141 - # this package FHS 2.2-compliant. For more information, see
142 - # https://www.pathname.com/fhs/
143 -#}
144 -
145 -# The following src_compile function is implemented as default by portage, so
146 -# you only need to call it, if you need different behaviour.
147 -#src_compile() {
148 - # emake is a script that calls the standard GNU make with parallel
149 - # building options for speedier builds (especially on SMP systems).
150 - # Try emake first. It might not work for some packages, because
151 - # some makefiles have bugs related to parallelism, in these cases,
152 - # use emake -j1 to limit make to a single process. The -j1 is a
153 - # visual clue to others that the makefiles have bugs that have been
154 - # worked around.
155 -
156 - #emake
157 -#}
158 -
159 -# The following src_install function is implemented as default by portage, so
160 -# you only need to call it, if you need different behaviour.
161 -#src_install() {
162 - # You must *personally verify* that this trick doesn't install
163 - # anything outside of DESTDIR; do this by reading and
164 - # understanding the install part of the Makefiles.
165 - # This is the preferred way to install.
166 - #emake DESTDIR="${D}" install
167 -
168 - # When you hit a failure with emake, do not just use make. It is
169 - # better to fix the Makefiles to allow proper parallelization.
170 - # If you fail with that, use "emake -j1", it's still better than make.
171 -
172 - # For Makefiles that don't make proper use of DESTDIR, setting
173 - # prefix is often an alternative. However if you do this, then
174 - # you also need to specify mandir and infodir, since they were
175 - # passed to ./configure as absolute paths (overriding the prefix
176 - # setting).
177 - #emake \
178 - # prefix="${D}"/usr \
179 - # mandir="${D}"/usr/share/man \
180 - # infodir="${D}"/usr/share/info \
181 - # libdir="${D}"/usr/$(get_libdir) \
182 - # install
183 - # Again, verify the Makefiles! We don't want anything falling
184 - # outside of ${D}.
185 -#}
186
187 diff --git a/skel.metadata.xml b/skel.metadata.xml
188 deleted file mode 100644
189 index 42444c655..000000000
190 --- a/skel.metadata.xml
191 +++ /dev/null
192 @@ -1,31 +0,0 @@
193 -<?xml version="1.0" encoding="UTF-8"?>
194 -<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
195 -<!--
196 -This is the example metadata file.
197 -The root element of this file is <pkgmetadata>. Within this element a
198 -number of subelements are allowed, the most common being maintainer.
199 -
200 -For a full description look at:
201 -https://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/
202 -
203 -Before committing, please remove the comments from this file. They are
204 -not relevant for general metadata.xml files.
205 --->
206 -<pkgmetadata>
207 -<maintainer type="person">
208 - <email>exampledev@g.o</email>
209 - <description>Primary maintainer</description>
210 -</maintainer>
211 -<maintainer type="project">
212 - <email>exampleproject@g.o</email>
213 - <name>Gentoo Example Project</name>
214 -</maintainer>
215 -<longdescription>Long description of the package</longdescription>
216 -<use>
217 - <flag name="aspell">Uses <pkg>app-text/aspell</pkg> for spell checking.
218 - Requires an installed dictionary from <cat>app-dicts</cat></flag>
219 - <flag name="flag">Description of how USE='flag' affects this package</flag>
220 - <flag name="userland_GNU">Description of how USERLAND='GNU' affects this
221 - package</flag>
222 -</use>
223 -</pkgmetadata>