RPMs packages

[GoogleCodeExporter]

Hello, I address the question whether you do not need RPM packages for
Fedora? These are holidays so I could make a bid for the creation of these:)

If you need to let me know.

Original issue reported on code.google.com by godlewsk...@gmail.com on 2 Jul 2009 at 8:35

[GoogleCodeExporter]

O, sorry for Type :)

Original comment by godlewsk...@gmail.com on 2 Jul 2009 at 8:36

[GoogleCodeExporter]

That sounds great, RPM packages would be really helpful. I think the only 
problem
would be that I have absolutely no experience with packaging (the gnome-colors
packagers take care of all the .debs, scripting and the PPA's), so if a new 
version
is released, I wouldn't want to inconvenience you after every release by asking 
for
updated rpm packages.

Perhaps if the creation of the .RPM's could be scripted, I could upload them 
after
the tarballs so users of rpm-based distros can get them. Also, for Fedora - the
current model that the Ubuntu PPA has would be ideal, as the packages are built 
with
a common dependency that has all common icons (which reduces unpacked size of 
all
color variants from 60MB to only 20MB).

In any case, I think if I can learn to package them on my end or they can be 
scripted
into some sort of makefile, I won't have to inconvenience anyone - and perhaps I
could add a few extra fedora additions, like using the tango-based fedora logo
included in the set for menus and branding instead of the gnome-colors logo.

Original comment by perfectska04 on 2 Jul 2009 at 9:25

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Packages needn't be maintained by upstream. There is a RSS feed for the download
section. That's the easiest way to stay up to date.

For gnome-colors I wrote two small scripts (create-gnome-colors-common and
update-index-theme). You can grab the latest version here [1].

In the Subversion repository you can find now Makefiles. They may help you.

[1]
http://bazaar.launchpad.net/~gnome-colors-packagers/gnome-colors-pkg/debian/file
s/head%3A/debian/

Original comment by benjamin.drung on 2 Jul 2009 at 10:37

[GoogleCodeExporter]

Thanks, Benjamin. I'll test the makefiles and mail you in a bit.

As for this issue, I guess using the RSS would work for other distros. If 
anything, I
just found that the .tar.gz files can be made installable in Fedora or any
GNOME-based distribution by simply renaming the extension to .gtp

Original comment by perfectska04 on 2 Jul 2009 at 10:56

• Changed state: WontFix

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The script looks great by Tuesday ready to give the package;) If you want to of 
course.

Original comment by godlewsk...@gmail.com on 3 Jul 2009 at 7:08

[GoogleCodeExporter]

If the script is not pre-packaging to make any difficulties, he would be if I 
had to
separate each directory copied. About new versions I can find the RSS feed:)

Create unless subpackages gnome-brave, gnome-human etc. This will be easier to
maintain order.

Original comment by godlewsk...@gmail.com on 3 Jul 2009 at 7:14

[GoogleCodeExporter]

@godlewski.piotr

Hey, sorry, I couldn't quite understand your second comment (perhaps a language
barrier, sorry)

"Create unless subpackages gnome-brave, gnome-human etc. This will be easier to
maintain order."

The RSS feed in the downloads can be used to monitor new releases, and the new
included makefiles can now install either as user or system-wide with "make 
install"
or "make user-install". I think with the makefiles installing from any Linux 
variant
should be easy enough from the tarball, but if you wish - rather than hosting
packages upstream, a Fedora repo with watch files and build/dependency scripts 
like
the PPA has would perhaps be best, since the ideal case for packages is 
updating from
a yum/apt repo (like how Opensuse contrib already hosts gnome-colors), rather 
than
sending users here to download a binary, which is much like simply getting the 
tarball.

Original comment by perfectska04 on 3 Jul 2009 at 9:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I also do not fully understand what you're saying). I understood that only the
installation you want to use the Makefile, but I still created the RPMs from the
gnome-colors create wallpaper tomorrow:)

Sorry for my english;) If you do not want packages that ok;)

http://alarm-clock.pl/piotrek-repo/other_stuff/

Original comment by godlewsk...@gmail.com on 10 Jul 2009 at 8:40

[GoogleCodeExporter]

Sorry if there's a misunderstanding, I just meant to say that for RPM packages a
repository is better so I can link to it, and it doesn't have to be maintained 
upstream!

Since the link you gave me is a repository, I can link to it for Fedora usage. 
If you
have a watch file for the repo, you can set it to download and build 
automatically
without requiring any further work on your end :)

I'd also recommend not using SVN but the stable distributable packages. 
Currently the
entire SVN is being restructured - so I believe it will be very unstable and 
even
break things until everything is settled.

Original comment by perfectska04 on 10 Jul 2009 at 8:53

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

These packages added to my personal repository. Tomorrow i will build a 
repository
for gnome-colors and build RPM package with .repo file.

Tomorrow i will build even Shiki-colors and arc-colors. ;)

Original comment by godlewsk...@gmail.com on 10 Jul 2009 at 9:00

[GoogleCodeExporter]

Ok, thanks for your work!
I'll link to the repo when it's done for Fedora users.

Original comment by perfectska04 on 10 Jul 2009 at 9:04

[GoogleCodeExporter]

The distributed tarballs contain the makefile, too. So your RPM packages does 
not
need many modifications to use the tarballs instead of SVN trunk.

If you have wishes for the makefile, please let me know.

Original comment by benjamin.drung on 10 Jul 2009 at 9:18

[GoogleCodeExporter]

I built almost all the packages, but I can not build Metacity (Easy, Striped) 
because
spaces are subdirectory names. You can do something with that?

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 9:54

[GoogleCodeExporter]

The problem is, that the directory name is used as name of the theme. We had 
problems
with the build tool for Debian packages, too, but it was possible to work around
them. Where does the problem lie?

Original comment by benjamin.drung on 11 Jul 2009 at 11:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Building a complete package. Yet one: Shiki-colors-murrine. I changed the name 
of
directories Metacity (Easy, Striped) in the Makefile, I added a '-'.

Set up three repositories: stable (with sources), update (updates), and testing 
(from
svn). These packages are not yet official first someone has to test them ;)

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 12:23

Attachments:

• gnome-colors.repo

[GoogleCodeExporter]

Indeed does not work. The problem for me is in the %files section, which does 
not
support spaces. The addition of characters "\" also does not give you anything. 
And
here I do not help it.

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 12:27

[GoogleCodeExporter]

I worked around this problem by using wildcards. Does the %files section allow 
wildcards?

Original comment by benjamin.drung on 11 Jul 2009 at 12:52

[GoogleCodeExporter]

I think that it but never used them, you can give an example?

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 12:56

[GoogleCodeExporter]

Replacing the space by an ? would be one solution. Shiki-Colors?Striped?Metacity
matches "Shiki-Colors Striped Metacity".

Original comment by benjamin.drung on 11 Jul 2009 at 1:09

[GoogleCodeExporter]

No that does not work. The %files section must specify the path to a file path
(directory names) are also the "?" and others.

I am not help here. You have to change the name of the motif that I can build 
the
package.

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 1:43

[GoogleCodeExporter]

What is the result of "ls /usr/share/themes/"? I have there other themes with 
spaces.
If you have them, too, there must be a solution.

Original comment by benjamin.drung on 11 Jul 2009 at 1:52

[GoogleCodeExporter]

[root@piotrek-fedora ~]# ls /usr/share/themes/
AgingGorilla       HighContrast                   Shiki-Brave
Atlanta            HighContrastInverse            Shiki-Colors-Easy-Metacity
Bright             HighContrastLargePrint         Shiki-Colors-Metacity
Clearlooks         HighContrastLargePrintInverse  Shiki-Colors-Striped-Metacity
ClearlooksClassic  Industrial                     Shiki-Dust
Crux               Inverted                       Shiki-Human
CurvyLooks         LargePrint                     Shiki-Noble
Default            LowContrast                    Shiki-Wine
Emacs              LowContrastLargePrint          Shiki-Wise
Esco               Metabox                        Simple
Fedora             Mist                           ThinIce
Glider             Nodoka
Glossy             Raleigh
[root@piotrek-fedora ~]# 

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 1:54

[GoogleCodeExporter]

Can you live with patching Shiki-Colors for the RPM, to replace the spaces to 
dashes?
You have to patch the index.theme files, too.

Original comment by benjamin.drung on 11 Jul 2009 at 2:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I cannot apply it. Better if they renamed permanently. Gnome doesn't recognize 
such a
motif, since there is no such catalogue. 

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 2:36

[GoogleCodeExporter]

Renaming it seems simple enough, but I'm not sure if it will break the makefile 
or
other existing installations. At worst, it might leave people who installed 
manually
with two copies of the metacities.

If Benjamin says it's safe, I can make the changes... If not, I guess another
solution can be found.

Original comment by perfectska04 on 11 Jul 2009 at 4:18

• Changed state: Started

[GoogleCodeExporter]

It's safe. Without spaces, the makefile would become simpler/shorter.

Original comment by benjamin.drung on 11 Jul 2009 at 5:31

[GoogleCodeExporter]

It's done. I replaced spaces for dashes and updated the index.theme files, so 
the
themes should recognize them. Makefiles might have to be updated, though.

Original comment by perfectska04 on 11 Jul 2009 at 5:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi, still bring Makefile up to date for Shiki-Colors ;) Will you enter changes 
into
4.3.1 or 4.3.2? 

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 6:10

[GoogleCodeExporter]

I'd update the makefile myself, but I'm afraid I might break something.

As for the changes - they will be entered into the next release. I can't say for
certain when it will be. From the side of the icons everything seems to be going
smoothly, but for Shiki and Arc, I'm still thinking what to do next, as GDM has 
been
deprecated for the next Ubuntu release, which was one of the last distributions 
to
stick to the old GDM framework.

It might be that Shiki and Arc are combined into a single package as a set of 
GTK
themes and wallpapers, or they might be left separate and the GDM part dropped, 
or
they might simply get the ability to be recolored automatically. There are 
simply too
many radical decisions to be made and it might take a while to get everything 
in order.

Original comment by perfectska04 on 11 Jul 2009 at 6:26

[GoogleCodeExporter]

The makefile is updated now.

Original comment by benjamin.drung on 11 Jul 2009 at 7:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I added files from SVN to the package and it works. Package added to the 
updates.
I'm going to holidays. I will return in next Sunday ;)

Original comment by godlewsk...@gmail.com on 11 Jul 2009 at 8:43

[GoogleCodeExporter]

I updated repositories updates and stable. Tonight I plan to add more packages 
to
testing (from SVN).I would like to build the Shiki-Colors Murrine but does not 
want
to work correctly, the evening will give an error code.

Original comment by godlewsk...@gmail.com on 20 Jul 2009 at 1:42

[GoogleCodeExporter]

If the repo has the stable packages, I can link to it! :)

BTW, what error comes out for shiki-murrine?

Original comment by perfectska04 on 20 Jul 2009 at 2:16

[GoogleCodeExporter]

No please, no. Still I have to improve a few significant errors, but errors. I
promise that later this week add to the repository in a 100% complete package.

At night I will give an error code, but also Clearlooks does not look the same 
as the
screen on the home page.

Original comment by godlewsk...@gmail.com on 20 Jul 2009 at 2:33

[GoogleCodeExporter]

Ok, I'll wait.

Clearlooks does not look the same as the home page, because the murrine version 
is
the one featured there. The clearlooks version should look pretty much the same 
as
murrine, with the difference being striped tabs - progressbars and scrollbars.

Could the error with the Murrine variant be that you don't have Murrine 0.9.3
installed? The Murrine version will not work without that specific version or 
later.

Original comment by perfectska04 on 20 Jul 2009 at 2:39

[GoogleCodeExporter]

Murrine version in repo: 0.53

Build a newer version of the most and brings it to the repo.

Original comment by godlewsk...@gmail.com on 20 Jul 2009 at 3:00

[GoogleCodeExporter]

Ok, the version from the repository rawhide work. But I do not know what will 
be for
older versions when newer version of the engine built, but probably the best 
option
is to build a RPM from a later version.

Original comment by godlewsk...@gmail.com on 20 Jul 2009 at 3:13

[GoogleCodeExporter]

I finished building packages.

I signed them GPG key one for each repository: stable, updates, testing.
All packages are created, in addition to-extras - also create them?

Mirrors are needed now because the server is not an emergency. The build was 
just me
gtk-murrine-engine version 0.90.3 for the F10 and F11.

It is, in principle, all share a GPG key that must be moved to 
/etc/pki/rpm-gpg/ a
file. Repos that should be given to the /etc/yum.repos.d

For shiki-colors and-shiki-colors-murrine gave meaning that the conflict can 
not be
installed together. ;)

Original comment by godlewsk...@gmail.com on 28 Jul 2009 at 8:33

Attachments:

• gnome-colors.repo
• RPM-GPG-KEY-gnome-colors-repo
• RPM-GPG-KEY-gnome-colors-testing
• RPM-GPG-KEY-gnome-colors-updates

[GoogleCodeExporter]

Here are the names of fixed keys. Shortly probably create the RPM package with 
.repo

Original comment by godlewsk...@gmail.com on 28 Jul 2009 at 8:59

Attachments:

• RPM-GPG-KEY-gnome-colors-repo-testing
• RPM-GPG-KEY-gnome-colors-repo
• RPM-GPG-KEY-gnome-colors-repo-updates

[GoogleCodeExporter]

Sorry for the late reply, yes - the clearlooks and murrine versions should 
conflict,
as they provide mostly the same content. There have been no new revisions of the
current murrine engine, so it should work for a few more release cycles - don't 
worry.

As for the repositories themselves, I don't know much about Fedora repos or even
repos in general, so once you're satisfied just tell me and let me know which 
link to
redirect Fedora users to :)

Original comment by perfectska04 on 3 Aug 2009 at 9:11

[GoogleCodeExporter]

FWIW, it seems like the GNOME-Colors icon theme is currently being reviewed[1] 
for
inclusion into the official Fedora repos.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=515280

Original comment by Theo...@gmail.com on 4 Aug 2009 at 3:19