[opensuse-buildservice] new package based on the existing one
Hello, after many years I'm back to Suse and would like to create new package which is based on some existing one, iow. take existing one, rename it and modify. What is the best way to accomplish it? I was reading 'tutorial' but not sure whether 'branch' command is the way to go? Sincerely, Gour -- From wherever the mind wanders due to its flickering and unsteady nature, one must certainly withdraw it and bring it back under the control of the self. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
osc copypac -- Later, Darin On Fri, Nov 28, 2014 at 3:21 PM, Gour <gour@atmarama.net> wrote:
Hello,
after many years I'm back to Suse and would like to create new package which is based on some existing one, iow. take existing one, rename it and modify.
What is the best way to accomplish it?
I was reading 'tutorial' but not sure whether 'branch' command is the way to go?
Sincerely, Gour
-- From wherever the mind wanders due to its flickering and unsteady nature, one must certainly withdraw it and bring it back under the control of the self.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On November 28, 2014 3:21:39 PM EST, Gour <gour@atmarama.net> wrote:
Hello,
after many years I'm back to Suse and would like to create new package which is based on some existing one, iow. take existing one, rename it and modify.
What is the best way to accomplish it?
I was reading 'tutorial' but not sure whether 'branch' command is the way to go?
Sincerely, Gour
I see no value in branching. I would just: osc copypac <old project> <old package> <new project> <new package> In general osc has a thousand options, so it can do most anything you need done related to managing OBS. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28.11.2014 Gour wrote:
I was reading 'tutorial' but not sure whether 'branch' command is the way to go?
If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend. Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from. Regards, Johannes - -- `But he knows your dad was right all along now about Voldemort being back -´ `Dumbledore says people find it far easier to forgive others for being wrong than being right,´ said Hermione. (Ron and Hermione in Harry Potter and the Half-Blood Prince) -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlR5e0AACgkQzi3gQ/xETbJS6QCgldLQrVB69bgSEXP103uPTkI6 2PsAn39ZWDZAcU6juXROxj8DlQgBKHEp =6AUu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl <mail@ojkastl.de> wrote: Thank you all for the help.
If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.
Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.
I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one. I did as advised and here is the package which works for me - I'm using it with Claws-mail with its bogofilter plugin. Result is here: https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite First I was changing spec file and submitting via web, then I did build package locally and commit. Please, advice/correct me!! No need to tell, but I'd like that bogofilter ends up in openSUSE since I was using the same package in FreeBSD (http://www.freshports.org/mail/bogofilter-sqlite/), in Arch Linux (https://aur.archlinux.org/packages/bogofilter-sqlite/) as well in Debian Sid (https://packages.debian.org/sid/bogofilter-sqlite) from where did I migrate to SUSE. Sincerely, Gour -- An intelligent person does not take part in the sources of misery, which are due to contact with the material senses. O son of Kuntī, such pleasures have a beginning and an end, and so the wise man does not delight in them.
Hi Gour, On Sat, Nov 29, 2014 at 12:49:21PM +0100, Gour wrote:
On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl <mail@ojkastl.de> wrote:
If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.
Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.
I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.
I did as advised and here is the package which works for me - I'm using it with Claws-mail with its bogofilter plugin.
Result is here:
https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite
First I was changing spec file and submitting via web, then I did build package locally and commit.
Please, advice/correct me!!
Maybe there is a better way to approach your goal by reusing the existing server:mail/bogofilter project. It should be possible to have server:mail/bogofilter-sqlite which links against server:mail/bogofilter and has a special package configuration in place. This setting would lead to the required --with-database=sqlite and the required BuildRequires: sqlite3-devel instead of db-devel The opposite we would set for the bogofilter package to keep the current default database. This approach would also prevent you from losing the ifarch arm setting later in the existing bogofilter spec file. I've not used the OBS meta pkg feature - set via osc meta command line - to solve an issue like this. Hints are highly welcome. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On November 29, 2014 6:49:21 AM EST, Gour <gour@atmarama.net> wrote:
On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl <mail@ojkastl.de> wrote:
Thank you all for the help.
If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.
Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.
I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.
I did as advised and here is the package which works for me - I'm using it with Claws-mail with its bogofilter plugin.
Result is here:
https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite
=> "Opensuse-factory" is no longer the preferred testing repo name. Drop it and add opensuse-tumbleweed. (Only announced a couple weeks ago, so most projects still use opensuse-factory, including mine, but you might as well start off with the new nomenclature). => On the WebUI near the build results you will find rpmlint results. The first 2 complaints you should fix before moving on. - change *.changes and *.spec to be named after the new package name. mv ... ... osc ar osc commit - do you really need to include "install" in the doc set? Fyi: just because the old package has rpmlint errors doesn't mean your new package should duplicate them.
First I was changing spec file and submitting via web, then I did build package locally and commit.
I try to do a local build of everything before I commit. I only locally build for opensuse-factory (I mean opensuse-tumbleweed) typically, then I commit working changes to OBS to verify the other distros I care about build correctly.
Please, advice/correct me!!
No need to tell, but I'd like that bogofilter ends up in openSUSE since I was using the same package in FreeBSD (http://www.freshports.org/mail/bogofilter-sqlite/), in Arch Linux (https://aur.archlinux.org/packages/bogofilter-sqlite/) as well in Debian Sid (https://packages.debian.org/sid/bogofilter-sqlite) from where did I migrate to SUSE.
Opensuse is a do-apoly - those that do decide. If you are willing to do the packaging work and commit to maintaining a package for the lifecycle of a release, then there are only 3 hurdles to overcome: - technical: does the packaging meet the opensuse guidelines? Does the package itself work? - legal: is the licensing either open source? If not, can a legal right to distribute be arranged? Also, is the package legal to distribute under both US and German law. German law prohibits pure hacking tools, so somethings legal in most countries are not allowed in opensuse. An example is metasploit; it would be a difficult sell to the release team to include it in factory, but it is legally distributed in the US. - security - some packages require a security review. I don't know when this is required/not required but I've got a package going through a security review now (my first). It won't be submitted to factory until that is complete. < http://bugzilla.opensuse.org/show_bug.cgi?id=900460>. Probably needed because it reaches out to Google during setup. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
I On November 29, 2014 6:49:21 AM EST, Gour <gour@atmarama.net> wrote:
On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl <mail@ojkastl.de> wrote:
Thank you all for the help.
If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.
Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.
I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.
I just realized, you probably don't want a standalone package like you created. Instead a sub-package is probably the best choice. Sub-packages are common with rpm/spec file based distros. I assume fedora has bogofilter-sqlite as a sub-package not a standalone package as well. [false - I just checked - <http://koji.fedoraproject.org/koji/buildinfo?buildID=554737> - at least that package does not have -salivate sub-package]. As an example of a spec file that generates several sub-packages look at the spec file for <https://build.opensuse.org/package/show/security:forensics/libewf> [it is one of the packages I maintain]. It generates a sub-package of python-libewf, which is a set of python bindings for libewf. Search the spec file for all references to python. They only exist to get that sub-package built. === If I'm right you should start over: Branch bogofilter Edit spec file to create bogofilter-sqlite sub-project Test osc vc # update the changes file with your changes Submit your changes back to the main biographer package. If accepted back to the development project, the maintainer will forward your SR to factory. Greg I -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sat, 29 Nov 2014 10:43:26 -0500 Greg Freemyer <greg.freemyer@gmail.com> wrote:
Instead a sub-package is probably the best choice. Sub-packages are common with rpm/spec file based distros.
I did some rpm-related reading about subpackages and not being sure whether I understood properly visited #rpm.org when I was told that one cannot have %build section per subpackage. Moreover, I was suggested to create a new package and use 'Conflicts' in each one. Remember, bogofilter and bogofilter-sqlite are actually *two different* and conflicting packages despite using the same source since both produce single executable, one uses (Berkeley) DB back-end and the other one uses Sqlite3. So, considering the above do you still consider that subpackage is the appropriate solution and if yes, can you give some hint how to have different invocation of ./configure for main and subpackage? Sincerely, Gour -- Therefore, without being attached to the fruits of activities, one should act as a matter of duty, for by working without attachment one attains the Supreme.
On Sun, Nov 30, 2014 at 09:49:47AM +0100, Gour wrote:
Greg Freemyer <greg.freemyer@gmail.com> wrote: I did some rpm-related reading about subpackages and not being sure whether I understood properly visited #rpm.org when I was told that one cannot have %build section per subpackage.
Moreover, I was suggested to create a new package and use 'Conflicts' in each one.
Remember, bogofilter and bogofilter-sqlite are actually *two different* and conflicting packages despite using the same source since both produce single executable, one uses (Berkeley) DB back-end and the other one uses Sqlite3.
So, considering the above do you still consider that subpackage is the appropriate solution and if yes, can you give some hint how to have different invocation of ./configure for main and subpackage?
Look at the php5 package. Subpackages will not work, if two (sub-)packages need to ship different content for one path. In that case, you could put two spec files in one OBS packages (see binutils/gcc). Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On November 30, 2014 6:49:56 AM EST, Martin Koegler <martin.koegler@chello.at> wrote:
Greg Freemyer <greg.freemyer@gmail.com> wrote: I did some rpm-related reading about subpackages and not being sure whether I understood properly visited #rpm.org when I was told that one cannot have %build section per subpackage.
Moreover, I was suggested to create a new package and use 'Conflicts' in each one.
Remember, bogofilter and bogofilter-sqlite are actually *two different* and conflicting packages despite using the same source since both produce single executable, one uses (Berkeley) DB back-end and the other one uses Sqlite3.
So, considering the above do you still consider that subpackage is
On Sun, Nov 30, 2014 at 09:49:47AM +0100, Gour wrote: the
appropriate solution and if yes, can you give some hint how to have different invocation of ./configure for main and subpackage?
Look at the php5 package.
Subpackages will not work, if two (sub-)packages need to ship different content for one path. In that case, you could put two spec files in one OBS packages (see binutils/gcc).
Regards, Martin
The kernel packages are another example of a single master package with multiple spec files. The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone. These are the kernel instructions I just copied from evergreen wiki page: == login=JohnDoe osc copypac Kernel:SLE11-SP1 kernel-source home:$login:Evergreen-11.1 for p in kernel-{default,desktop,pae,xen,vanilla,syms}; do osc linkpac -C copy home:$login:Evergreen-11.1 kernel-source home:$login:Evergreen-11.1 $p done == In this case bogofilter and bogofilter-sqlite would be linked packages. You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.) The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, 30 Nov 2014 09:29:19 -0500 Greg Freemyer <greg.freemyer@gmail.com> wrote: Hello Greg, excuse me for not replying earlier...I hit some btrfs bug, lost my parition, had to re-install, restore (older) backup from tapes, re-configure eveything etc.
The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone.
OK. That's clear.
In this case bogofilter and bogofilter-sqlite would be linked packages.
I did the above - linkpac and checkout stuff into my folder @localhost.
You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec
Now some questions: 1) is it required to use 'linkpac -C copy' when doing linkpac? 2) when I do linkpac, I end up with bogofilter.spec in the bogofilter-sqlite folder, so I wonder how should I create bogofilter-sqlite.spec, iow. is it actually just modified spec file incorporating required changes to build it? 3) does bogofilter-sqlite folder contain both spec files?
The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.)
4) how should one do the build, by running 'osc build bogofilter.spec' ?
The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both.
It sounds good. Otoh, I was looking for help in IRC today (#opensuse-buildservice) and I was suggested (darix provided example) to use update-alternatives mechanism in order so that different users can use different packages installed simultenaously and in that case binary would be bogofilter-sqlite instead of default bogofilter? Please, advice! Sincerely, Gour -- -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Gour <gour@atmarama.net> writes:
1) is it required to use 'linkpac -C copy' when doing linkpac?
This is the default when creating a link within the same project. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 9, 2014 at 1:46 PM, Gour <gour@atmarama.net> wrote:
On Sun, 30 Nov 2014 09:29:19 -0500 Greg Freemyer <greg.freemyer@gmail.com> wrote:
Hello Greg,
excuse me for not replying earlier...I hit some btrfs bug, lost my parition, had to re-install, restore (older) backup from tapes, re-configure eveything etc.
The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone.
OK. That's clear.
In this case bogofilter and bogofilter-sqlite would be linked packages.
I did the above - linkpac and checkout stuff into my folder @localhost.
You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec
Now some questions:
1) is it required to use 'linkpac -C copy' when doing linkpac?
I'm not positive
2) when I do linkpac, I end up with bogofilter.spec in the bogofilter-sqlite folder, so I wonder how should I create bogofilter-sqlite.spec, iow. is it actually just modified spec file incorporating required changes to build it?
Yes, the second one is just a copy of the first with modifications.
3) does bogofilter-sqlite folder contain both spec files?
Yes, both packages will contain both spec files. the package "bogofilter" will use spec file "bogofilter.spec" the package "bogofilter-sqlite" will use spec file "bogfilter-sqlite.spec" That will happen automatically if you have 2 projects and the spec files are named after the projects.
The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.)
4) how should one do the build, by running 'osc build bogofilter.spec' ?
"osc build" is fine. osc knows what project you are trying to build and will select the matching spec file automatically.
The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both.
It sounds good.
Otoh, I was looking for help in IRC today (#opensuse-buildservice) and I was suggested (darix provided example) to use update-alternatives mechanism in order so that different users can use different packages installed simultenaously and in that case binary would be bogofilter-sqlite instead of default bogofilter?
Please, advice!
Above my pay grade. I've never setup an update-alternatives situation.
Sincerely, Gour
Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, 9 Dec 2014 17:22:23 -0500 Greg Freemyer <greg.freemyer@gmail.com> wrote:
Yes, the second one is just a copy of the first with modifications.
OK.
Yes, both packages will contain both spec files.
So, considering that after I linkpac-ed bogofilter to bogofilter-sqlite and then checkout out it locally, and that there is already bogofilter.spec in the checkout out sources, it means that I have to add bogofilter-sqlite.spec file to both packages?
"osc build" is fine. osc knows what project you are trying to build and will select the matching spec file automatically.
That's still a magic for me, but I believe you. ;)
Above my pay grade. I've never setup an update-alternatives situation.
OK. I'll postpone it for later then. This setup looks seems to be simpler. Here you can see result of my attempts: https://build.opensuse.org/project/show/home:gour Does it look good in regard to main package with the linked one? Sincerely, Gour -- Perform your prescribed duty, for doing so is better than not working. One cannot even maintain one's physical body without work. -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 9, 2014 at 6:02 PM, Gour <gour@atmarama.net> wrote:
On Tue, 9 Dec 2014 17:22:23 -0500 Greg Freemyer <greg.freemyer@gmail.com> wrote:
Yes, the second one is just a copy of the first with modifications.
OK.
Yes, both packages will contain both spec files.
So, considering that after I linkpac-ed bogofilter to bogofilter-sqlite and then checkout out it locally, and that there is already bogofilter.spec in the checkout out sources, it means that I have to add bogofilter-sqlite.spec file to both packages?
"osc build" is fine. osc knows what project you are trying to build and will select the matching spec file automatically.
That's still a magic for me, but I believe you. ;)
Above my pay grade. I've never setup an update-alternatives situation.
OK. I'll postpone it for later then. This setup looks seems to be simpler.
Here you can see result of my attempts:
https://build.opensuse.org/project/show/home:gour
Does it look good in regard to main package with the linked one?
Almost: Look at <https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite> In the upper right corner it says there is a "link diff" between the 2 packages. We don't want that, but you MUST solve it via a SR. To create a SR from the WebUI, click on the blue "link diff" text. When the new page comes up, first review it and make sure you want to submit those changes to "bogofilter". If so, scroll down to the bottom and click "Submit to home:gour / bogofilter" Since you are the maintainer of "home:gour / bogofilter" you will receive a notification that a SR (submit request) has been sent to relative to bogofilter. You will need to accept that SR. Hope that makes sense, Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Greg Freemyer <greg.freemyer@gmail.com> writes:
If so, scroll down to the bottom and click "Submit to home:gour / bogofilter"
There is no point in submitting a linked package. Instead, edit home:gour/bogofilter directly. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, 10 Dec 2014 08:56:28 +0100 Andreas Schwab <schwab@suse.de> wrote:
There is no point in submitting a linked package. Instead, edit home:gour/bogofilter directly.
Hmm, now I'm confused... Sincerely, Gour -- One who is not disturbed in mind even amidst the threefold miseries or elated when there is happiness, and who is free from attachment, fear and anger, is called a sage of steady mind. -- From anger, complete delusion arises, and from delusion bewilderment of memory. When memory is bewildered, intelligence is lost, and when intelligence is lost one falls down again into the material pool. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Gour <gour@atmarama.net> writes:
3) does bogofilter-sqlite folder contain both spec files?
Forget about the bogofilter-sqlite directory once you've created the link. All edits go to the original package directory. Also, you need to create bogofilter-sqlite.changes which records the changes for the bogofilter-sqlite package. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, 10 Dec 2014 09:02:13 +0100 Andreas Schwab <schwab@suse.de> wrote:
Forget about the bogofilter-sqlite directory once you've created the link. All edits go to the original package directory.
Does it mean that after I do linkpac, I need only top checkout bogofilter and there add bogofilter-sqlite.spec?
Also, you need to create bogofilter-sqlite.changes which records the changes for the bogofilter-sqlite package.
That one also goes just in bogofilter directory? Sincerely, Gour -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On December 10, 2014 7:05:34 AM EST, Gour <gour@atmarama.net> wrote:
On Wed, 10 Dec 2014 09:02:13 +0100 Andreas Schwab <schwab@suse.de> wrote:
Forget about the bogofilter-sqlite directory once you've created the link. All edits go to the original package directory.
Does it mean that after I do linkpac, I need only top checkout bogofilter and there add bogofilter-sqlite.spec?
Also, you need to create bogofilter-sqlite.changes which records the changes for the bogofilter-sqlite package.
That one also goes just in bogofilter directory?
Sincerely, Gour
Andreas is saying you should do all edits/changes directly in bogofilter. They will be inherited by bogofilter-sqlite. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Gour <gour@atmarama.net> writes:
I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.
It would make much more sense to add a subpackage to the bogofilter package, since you are using identical sources just with a different configuration. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (8)
-
Andreas Schwab -
Andreas Schwab -
Darin Perusich -
Gour -
Greg Freemyer -
Johannes Kastl -
Lars Müller -
Martin Koegler