Mailinglist Archive: opensuse-buildservice (252 mails)

< Previous Next >
[opensuse-buildservice] more newby questions: project / package structure?
  • From: Andreas Jellinghaus <aj@xxxxxxxxxxxxxxx>
  • Date: Fri, 22 Sep 2006 09:18:42 +0200
  • Message-id: <45138E52.1060203@xxxxxxxxxxxxxxx>

how are projects and packages structured?
is it a fixed "one name for the project and then one for the package" system, or are further subdirs possible?

I wonder about this: recent discussions with rpm experts have shown me that merging several spec files into one only creates a horrible maintainence hell. also they have compelling arguments, that one rpm for all distributions was something they tried for years with lots of work, and it never worked well.

so I see as best solution to have codenames (e.g. fc3,fc4,fc5, sles9, sles10, oss10.0, dapper, edgy, etch, sarge, ...) and for each distribution *.spec.$codename or *.diff.gz.$codename. but this would require work on the build system side, and I get the impression noone wants that.

the alternative from my side would be per distro packages.
e.g. instead of "openct" I could have packages "openct.fc" and "openct.os" and "openct.sles" and "openct.sarge" and so on,
upload spec files for each. this wouldn't require changes in the code base, and give me the flexibility I need, so I can simply build new packages for my open source projects, with minimal changes to the last
spec file the distribution provides.

but that way the list of packages might grow very long. is it possible
to structure projects/packages a different way (i.e. path mechanism,
no flat one project, one package subdir structure)?

Regards, Andreas
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >